Re: [Gnumed-devel] More lab test result considerations: groupings

[lkcl]

Jim Busser wrote:
> 
> The lab results in BC CA include the HL7 message segment OBR 004  
> "Universal Service ID" of the form "Test code^Test name" for example  
> "LYTE^Electrolytes".
> 
> The thing to note is that a *single test code* can represent  
> *multiple results* that will be received.
> 
> IOW this OBR can be followed, in the same message, by multiple OBX  
> records for example
> 
> OBX|1|NM|2951-2^Sodium||140|mmol/L|135 - 145|N|||F|||20001101105900
> OBX|2|NM|2823-3^Potassium||5.0|mmol/L|3.5 - 5.0|H|||F|||20001101105900
> 

and then, also, multiple OBRs can be in the same message.  in other words,
it's a two-level hierarchy.

i have catered for this in business/GMHL7.py by creating one patient
"encounter" per OBR, and then storing test results (OBXs) on a per-encounter
basis.  in this way, the hierarchy is preserved.

the only thing is: at any time where messages (updates) are received which
do NOT match up with prior ones (missing OBRs), the hierarchy WILL be
destroyed.  so, jim, karsten, sebastien, anyone: have you actually seen any
HL7 data where HL7 updates do NOT contain the exact same OBR-OBX hierarchy? 
it's important to know.

l.

-- 
View this message in context: 
http://old.nabble.com/More-lab-test-result-considerations%3A-groupings-tp15399784p29382729.html
Sent from the GnuMed - Dev mailing list archive at Nabble.com.