I take it as tenant of faith that proprietary systems had their shot at "the
throne" and have missed it so badly that "the throne" will be held someday
by a FOSS system... making my comment about OSCAR more reasonable...
-FT
On 5/7/06, Will Ross <[EMAIL PROTECTED]> wrote:
>
> Fred,
>
> First o
Tim.Churches wrote:
>
> Tim (or anyone else familiar with OSCAR),
>
> Can you elaborate on this? What sort of data is being stored solely in
> PDFs, presumably as BLOBs in a table, or in the filesystem with pointers
> to them in a table? I can conceive of several circumstances in which
> stor
Andrew Schamess wrote:
> Thank you! It sounds like a very good EMR, though the fact that it's
> configured for a Canadian billing system may rule it out for me... In any
> case the info is very helpful. Thanks again.
>
Fred, any more thoughts on FreeB integration with OSCAR?
--
Jel
Yep... either someone needs to hire me (always a good idea! go to
SynSeer.com)... or someone with motivation and skill needs to start hacking
on it, getting questions answered by visiting my FreeB support forum
(subsection of the MirrorMed.org forums).
-FT
On 5/8/06, Jel Coward <[EMAIL PROTEC
On Mon, May 08, 2006 at 01:33:13PM -0700, Jel Coward wrote:
> OSCAR stores data in one place that is then pulled (as a view and for data
> entry) to 'populate' Chronic Disease Management 'forms'. The 's are there
> because the 'forms' are just a view on the data. THis allows single data
>
--- In openhealth@yahoogroups.com, "Fred Trotter" <[EMAIL PROTECTED]>
wrote:
>
> I take it as tenant of faith that proprietary systems had their shot
at "the
> throne" and have missed it so badly that "the throne" will be held
someday
> by a FOSS system... making my comment about OSCAR more reas
Hi all,
I'm collating standards (open or otherwise) that are being used in open
source health applications.
I'd appreciate if the developers on the list would explicitly publish what
standards they base their applications on and perhaps we can establish
interoperability from thereon.
For CHIT
Yes Will, OSCAR is written in Java (and uses MySQL for
its database engine). The drug database web-engine is
written in python (using the drugref project engine
which uses PostgreSQL as the database engine). OSCAR
is a very complex project. It is certainly capable of
being deployed in very large
P.S. OSCAR's main aim is NOT to sit on any throne but
to help patients. Our programmers are reminded
regularly to that very fine point;-)
David
--- Will Ross <[EMAIL PROTECTED]> wrote:
> Fred,
>
> First of all, a question (showing my ignorance) --
> OSCAR is written
> in Java?
>
> Second
In Canada we are watching closely the development of
standards from the Canada Health Infoway. I sit on
their Lab Standards group. Messaging standard will
most likely be HL7v3 and terminology standard will
likely be a combination of LOINC and SNOMED-CT.
David
--- [EMAIL PROTECTED] wrote:
> Hi
I think we agree that really is all about helping patients.. still no matter
what your goals are... its good to be the king.
Thanks for the development update. I am to disconnected from the OSCAR
market.
-FT
On 5/8/06, David Chan <[EMAIL PROTECTED]> wrote:
>
> P.S. OSCAR's main aim is NOT to
As most of you know by now, OpenEMed uses a service oriented architecture
based on the OMG PIDS/COAS/RAD/LQS standards, with PIDS using
by default the HL7 2.3 PID segment of patient identification. COAS uses
various HL7 codes for observations (or any other coding system that is
available).
L
12 matches
Mail list logo
