Paul wrote:
A wise quote that I heard when I started medical informatics training
was a lot of what we practice today is wrong. I'm a pediatrician,
and I can attest to this... and because of the constant evolution in
best practices, there's always a scattergram of practice styles vs.
best
Nandalal Gunaratne wrote:
Thank you Thomas. This is not urinalysis but urea and
electrolytes!
What is the Any Result data type is not set doing
here. It is, after all, urea and electrolytes, and the
electrolytes are mentioned. Is this to leave room for
rare electrolytes like the level of
February 2007 11:03
To: openhealth@yahoogroups.com
Subject: Re: [openhealth] Re: Hi folks.. OSHCA conference
Thanks for your offer Paul. You've probably missed OSHCA's call for
presentation at its coming conference from May 8-11 2007 in Kuala
Lumpur. The date had been changed from May 1 to accommodate
Hi Thomas,
--- In openhealth@yahoogroups.com, Thomas Beale [EMAIL PROTECTED] wrote:
Nandalal Gunaratne wrote:
The power of this approach is hard to appreciate
until you're in a
situation where lots of people have lots of things
they want to
characterize in a system. It allows
Thank you Thomas. This is not urinalysis but urea and
electrolytes!
What is the Any Result data type is not set doing
here. It is, after all, urea and electrolytes, and the
electrolytes are mentioned. Is this to leave room for
rare electrolytes like the level of copper in the
blood or iron?
Paul,
This is a good explanation of what OpenMRS is about,
and I find it quite refreshing. The problem of
constraints to allow greater acceptance and accuracy
(OpenEHR) against allowing change as you seem to do to
allow freedom to improve and grow in new directions,
but which can cause confusion
Nandalal Gunaratne wrote:
Paul,
This is a good explanation of what OpenMRS is about,
and I find it quite refreshing. The problem of
constraints to allow greater acceptance and accuracy
(OpenEHR) against allowing change as you seem to do to
allow freedom to improve and grow in new
Heya Tim,
--- In openhealth@yahoogroups.com, Tim Churches [EMAIL PROTECTED] wrote:
Yes, it seems to me that openEHR as it stands is an interesting and
potentially useful technical advance which permits greater semantic
precision and thus may ease the valid interchange of health data, but
--- In openhealth@yahoogroups.com, Will Ross [EMAIL PROTECTED] wrote:
Paul,
See below.
- - - - - - - -
Can the OCC be accessed by non-OpenMRS sites? And, as a corollary,
can non-OpenMRS sites contribute to the concept coop?
Thanks!
- - - - - - - -
Hi Will,
We certainly
Paul wrote:
Heya Tim,
--- In openhealth@yahoogroups.com, Tim Churches [EMAIL PROTECTED] wrote:
Yes, it seems to me that openEHR as it stands is an interesting and
potentially useful technical advance which permits greater semantic
precision and thus may ease the valid interchange of
The power of this approach is hard to appreciate
until you're in a
situation where lots of people have lots of things
they want to
characterize in a system. It allows non-developers
to own and
augment their own notions of what data matters to
them, without
altering the underlying
Tim Churches wrote:
It will be very interesting to see what the UK NHS does with the
copyright and licensing of openEHR archetypes and specifications which
it creates. It doesn't really have much of a track record for releasing
its IP for wider use, does it? (Very few large govt health
Joseph Dal Molin wrote:
Open source efforts/software like OpenMRS, WorldVistA (VistA Office
etc.), OSCAR etc. that are focused on diffusion/uptake and continuous
improvement. All need to have practical tools methods etc. to work
effectively in the heterogeneous health IT ecosystem. Building
On Tue, Feb 20, 2007 at 07:25:28AM +1100, Tim Churches wrote:
No, we need the data in computable form
OK, that kills the easy solution. Or it might not. If you
don't blend both sources of information (background image
and user input) but rather keep them separate and blend on
David Forslund wrote:
Joseph Dal Molin wrote:
Open source efforts/software like OpenMRS, WorldVistA (VistA Office
etc.), OSCAR etc. that are focused on diffusion/uptake and continuous
improvement. All need to have practical tools methods etc. to work
effectively in the heterogeneous health
Tim Churches wrote:
David Forslund wrote:
Joseph Dal Molin wrote:
Open source efforts/software like OpenMRS, WorldVistA (VistA Office
etc.), OSCAR etc. that are focused on diffusion/uptake and continuous
improvement. All need to have practical tools methods etc. to work
Karsten Hilbert wrote:
On Tue, Feb 20, 2007 at 07:25:28AM +1100, Tim Churches wrote:
No, we need the data in computable form
OK, that kills the easy solution. Or it might not. If you
don't blend both sources of information (background image
and user input) but rather keep them separate and
ksbhaskar wrote:
--- In openhealth@yahoogroups.com, Tim Churches [EMAIL PROTECTED] wrote:
[KSB] ...snip...
But if anyone can suggest an alternative for turning data recorded on
paper forms into data (as opposed to raster image) files, we'd love to
hear of it.
[KSB] Did you look at
Karsten Hilbert wrote:
On Tue, Feb 20, 2007 at 08:16:07AM +1100, Tim Churches wrote:
The data retrieved from step 4 will be computable data ! Not
particularly well constrained, but not just image data either.
Ah, OK. Our problem is that many users only want to record data with a
pen, on
Nandalal Gunaratne wrote:
The power of this approach is hard to appreciate
until you're in a
situation where lots of people have lots of things
they want to
characterize in a system. It allows non-developers
to own and
augment their own notions of what data matters to
them,
Tim Churches wrote:
Paul wrote:
We made a fairly conscious decision for
example, not to try to represent the HL7 RIM, as it's been our
experience that work in that domain is high on promise but lacking in
successful, well vetted implementations. If on the other hand, you
believe there's
This is just the type of discussion we should have in
the May OSHCA Conference!!
FOSS interoperability - from theory to practice
Nandalal
--- David Forslund [EMAIL PROTECTED] wrote:
Tim Churches wrote:
Paul wrote:
Hi Dave,
Our API is built around the standard health
objects
You're right, Nandalal. I was given the contact to the OpenMRS to invite
them to the OSHCA conference in May by the new director of ICT for IDRC
as I understand that the project in Africa is quite exciting. As soon as
I get a firm commitment on the funding for scholarships for those
outside
Hi Molly, I'm one of the co-founders of OpenMRS. Let me know how I
can be helpful to you. Still trying to catch up with the community
here, and it seems I need to do some due diligence on OSHCA.
Best,
-Paul
--- In openhealth@yahoogroups.com, Molly Cheah [EMAIL PROTECTED] wrote:
You're right,
What a wonderful discussion. I am so glad to have Regenstrief's
OpenMRS at the table! I also know there are other lurkers out there
(you know who you are!) who can add to the robust discussion. But my
purpose here is to highlight one point. Paul, Dave and Tim have all
mentioned not
Open source efforts/software like OpenMRS, WorldVistA (VistA Office
etc.), OSCAR etc. that are focused on diffusion/uptake and continuous
improvement. All need to have practical tools methods etc. to work
effectively in the heterogeneous health IT ecosystem. Building on Tim's
view:
I
Tim Churches wrote:
David Forslund wrote:
I was referring to making aspects such as the user interface and
business logic as general as possible, while still keeping users happy
by providing a slick, fiendly and productive interface and associated
conveniences. Inter-system
David Forslund wrote:
It does appear that programming languages seem to be the biggest barrier
for this particular open source community. Some like Java, some like Python,
some like PHP,
etc. That was the value of the IDL used in COAS, because it is language
independent
and really
Karsten Hilbert wrote:
On Sun, Feb 18, 2007 at 05:32:54PM +1100, Tim Churches wrote:
surprisingly tricky and fragile). But it does support dataset
versioning, so that the latest version of source data can be loaded into
a new dataset in the background while users continue to use an existing
Thomas Beale wrote:
Tim Churches wrote:
The openEHR model is probably relevant - it can be viewed as a more
evolved form of the two-level model which OpenEMR (and the Regenstrief
Clinic for several decades before that) uses. The openEHR people have
put forward their work as the basis for an
Tim Churches wrote:
Karsten Hilbert wrote:
Well, the path of least resistance here is to scan it and
use it as a background image in some text editor or other so
that what you type appears to be written into the fields
while it is (technically) written on top of the background
image. We then
UCLA had developed a very good scanning OCR solution . but I don't
think it was pure FOSS will ask.
Joseph
Tim Churches wrote:
Tim Churches wrote:
Karsten Hilbert wrote:
Well, the path of least resistance here is to scan it and
use it as a background image in some text editor or
Hi Tim, thanks for your interest in investigating collaborating with
us.
--- In openhealth@yahoogroups.com, Tim Churches [EMAIL PROTECTED] wrote:
NetEpi Analysis was designed to deal with the types of data and
analyses
which you mention - for example, apart from supporting complex
cross-tabs
Hi Karsten,
--- In openhealth@yahoogroups.com, Karsten Hilbert
Agree. I'm reading this thread with interest. I have been
interested in the Concept Dictionary approach ever since I
learned about OpenMRS a year ago or so. There's a strong
camp opposed to EAV-only schemata. I have a nagging
Molly, thanks for the information. I've passed this information onto
my colleagues and I'll let you know their thoughts soon.
Best,
-Paul
--- In openhealth@yahoogroups.com, Dr Molly Cheah [EMAIL PROTECTED] wrote:
Thanks for your offer Paul. You've probably missed OSHCA's call for
Paul wrote:
Thanks for this overview. There are so many layers to this whole
data analysis aspect of medical record repositories. Thinking from
left to right, there's the whole set of challenges around
converting stacked database models (where there's one row per
clinical observation)
Hi Dave,
Our API is built around the standard health objects within the
OpenMRS data model (ie, person, encounter, order, observation, etc) ,
as a way of abstracting out CRUD-type operations to the database.
There are layers of API calls on top of this bedrock which provide
business type
Paul wrote:
Hi Dave,
Our API is built around the standard health objects within the
OpenMRS data model (ie, person, encounter, order, observation, etc) ,
as a way of abstracting out CRUD-type operations to the database.
There are layers of API calls on top of this bedrock which provide
Tim Churches wrote:
Paul wrote:
Hi Dave,
Our API is built around the standard health objects within the
OpenMRS data model (ie, person, encounter, order, observation, etc) ,
as a way of abstracting out CRUD-type operations to the database.
There are layers of API calls on top of this
Hi Tim,
Part of the challenge our team continually struggles with involves
finding that right balance between being pragmatic and creating a
framework that's everything to everyone, and potentially smolders
under it's own weight.
Yes, this is an absolutely central problem, and we also
David Forslund wrote:
I've seen no real
effort in the open source community to embrace interoperability.
Certainly interoperability has
been opposed by much of industry until recently, but there is no good
reason for the open source community to not embrace it.
Dave, interoperability,
--- In openhealth@yahoogroups.com, Tim Churches [EMAIL PROTECTED] wrote:
Paul wrote:
We would love to hear from folks, in particular who have the following
skill sets:
1) database performance optimization
2) OLAP / reporting database design
3) Hibernate ORM
With respect to 2),
Tim Churches wrote:
David Forslund wrote:
I've seen no real
effort in the open source community to embrace interoperability.
Certainly interoperability has
been opposed by much of industry until recently, but there is no good
reason for the open source community to not embrace it.
Paul wrote:
Dave,
Thanks for your thoughts. These discussions can get religious fairly
quickly, so I'll just say that the bottom line for us is a simple one:
we're supporting an open-source collaboration less to meet/support
longstanding specifications that have fairly low uptake to this
44 matches
Mail list logo
