TEXTURAL RESULTS TO QUANTITIES The result of this analysis is that sometimes a single leaf in a tree will be reported as haemolysed rather than its numeric value - example: the results of an electrolyte measurement might have safe results for all analytes apart from potassium - the result will be 'haemolysed'. This can occur in haematology and other situations - reporting is required for medicolegal and billing purposes.
This presents a problem. We have a number of possibilities at our fingertips - perhaps the most important being the ability to mark something as unsafe for automatic processing. At the moment, I believe, this is limited to the ENTRY. If we take the CDA line of structured data and display - this would mean the display said haemolysed, the data would say 9.5 mmol/L but it would be marked as unsafe for automatic processing. The query would have to check the automatic processing flag - but this will be necessary anyway - but it will lead to a differential between the view provided in the display and the query. My belief is that results that are incorrect should not be there if at all possible - so I would like to see a means of being able to put the potassium in as haemolysed. This would mean a generic node with an ID that could have a textural term data type in biochemistry - and still have the text and even the LOINC code attached - but have a different nodeID so it would not be returned in the query - unless you were just searching on LOINC codes independent of the archetype. This will look a little clunky in the archetype itself and I will need to discuss the technical issues with Thomas. Cheers, Sam ____________________________________________ Dr Sam Heard Ocean Informatics, openEHR Co-Chair, EHR-SIG, HL7 Chair EHR IT-14-9-2, Standards Australia Hon. Senior Research Fellow, UCL, London 105 Rapid Creek Rd Rapid Creek NT 0810 Ph: +61 417 838 808 sam.heard at bigpond.com www.openEHR.org www.HL7.org __________________________________________ - If you have any questions about using this list, please send a message to d.lloyd at openehr.org
