On 2011/11/02 07:09 PM, Bill Lober wrote:
We’ve used LOINC for test and result codes.
Thanks Bill, appreciated. LOINC looks 1st choice
Very open, lots of information, too much, and more complicated to
implement than initially thought. Re "direction/tips &
tricks", I'll need some to cut our way through this! I could not
straight away find an OpenELIS developers' mailing list and Paul
I hope it is OK to harass you too:
How did you implement LOINC on DB design and functional levels?
My newbie guesses and questions:
1. Scan all the
LOINC codes for the ones we need? Would I find all of them in
the
top 2000 list?
2. Do we apply
these only to Analyses
only or are other objects
such as Analysis Requests/Orders, Patients, Doctors,
Clinics/Hospitals/Wards also affected?
3. Modify DB to link/include those (and keep it
flexible to allow for other vocabularies too)
4. Is it sufficient to use just the LOINC codes in comms from
there on or do we need to include any of the other fields?
(LOINC_NUM, LongName, SHORTNAME, CLASS, Rank)
Never a dull moment
Bests
l
--
You received this message as subscriber to the "Bika Health"
group. To post, send email to address@hidden.
To unsubscribe, mail address@hidden.
For more options, visit this group at http://groups.google.co.za/group/bika-health?hl=en
|