10.07.2015 Views

V3 Laboratory Domain Overview „Lab Report“ Localization in ... - HL7

V3 Laboratory Domain Overview „Lab Report“ Localization in ... - HL7

V3 Laboratory Domain Overview „Lab Report“ Localization in ... - HL7

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>V3</strong> <strong>Laboratory</strong> <strong>Doma<strong>in</strong></strong> <strong>Overview</strong><strong>„Lab</strong> <strong>Report“</strong> <strong>Localization</strong> <strong>in</strong> SwitzerlandDr. Andrzej J. KnafelRoche Instrument CenterCH-6343 Rotkreuz, Switzerlandandrzej.knafel@roche.com


Current <strong>V3</strong> Ballot <strong>Laboratory</strong> <strong>Doma<strong>in</strong></strong> ...1. In comparison with previous ballots, the scope of the<strong>Laboratory</strong> <strong>Doma<strong>in</strong></strong> for this ballot has be drasticallyreduced.2. Most of the artifacts found <strong>in</strong> this ballot are <strong>in</strong>tended tosupport a s<strong>in</strong>gle storyboard, which represents the mostcommon (or normal) flow of <strong>in</strong>formation <strong>in</strong>volved <strong>in</strong><strong>Laboratory</strong> communication.November 2002 A. Knafel 2


<strong>V3</strong> Lab Ref<strong>in</strong>ed Message Information ModelOrdersObservationsNovember 2002 A. Knafel 4


<strong>V3</strong> Lab Order/Observation – Model SkeletonTest Def<strong>in</strong>itionTest OrdersComb<strong>in</strong>ation ofs<strong>in</strong>gle testsTest ResultsNovember 2002 A. Knafel 5


<strong>V3</strong> <strong>Laboratory</strong> Basics Def<strong>in</strong>itions• An observation order is a request for the performance ofa test or observation.– Typically the request is made by a cl<strong>in</strong>ician or the laboratoryperform<strong>in</strong>g, and recorded with<strong>in</strong> one computer system, andthen transmitted to a second system for performance.– In some cases, the order is transmitted by other means, i.e.,<strong>in</strong>formation related to that order may or may not be recorded.• An observation event records the performance of a testor observation.– Typically the observation is performed by one or more personsor, perhaps, a device, recorded with<strong>in</strong> one computer system,and then transmitted to a second system for storage and/or use.November 2002 A. Knafel 6


<strong>V3</strong> Lab Application Roles1. Observation Order Global Placer Observation2. Order Global Fulfiller3. Observation Promise Global Confirmer4. Observation Promise Global Confirmation Receiver5. Observation Promise Global Informer6. Observation Promise Global Tracker7. Observation Event Global Informer8. Observation Event Global TrackerNovember 2002 A. Knafel 7


<strong>V3</strong> Lab Trigger Events1. Observation Order Activate, Fulfillment Request2. Observation Order Activate, Rejection3. Observation Promise Activate, Confirmation4. Observation Promise Complete, Notification5. Observation Event Activate, Notification6. Observation Event Complete, NotificationNovember 2002 A. Knafel 8


<strong>V3</strong> Lab Message and Interaction ExamplesMessage TypeObservation OrderActiveObservation PromiseCompleteObservation PromiseActiveObservation EventCompleteObservation EventActiveInteractionFulfillment Request(Lab order request)Notification(Unsolicited lab committment msg)Confirmation(Lab commitment as response to query)Notification(Unsolicited send<strong>in</strong>g of ready lab results)Notification(Unsolicited <strong>in</strong>fo: scheduled process<strong>in</strong>g)November 2002 A. Knafel 9


<strong>HL7</strong> Switzerland – <strong>Laboratory</strong> <strong>V3</strong> ProjectObjective:– Harmonize between <strong>HL7</strong> and Swiss proprietary XMLproposals for„Transfer of laboratory orders, results and f<strong>in</strong>d<strong>in</strong>gs“.– „Localize“ the <strong>Laboratory</strong> <strong>Doma<strong>in</strong></strong> <strong>V3</strong> messages <strong>in</strong>Switzerland.November 2002 A. Knafel 10


<strong>HL7</strong> CH – “Lab Report <strong>V3</strong>” Project Status• Current R-MIMs analyzed and localized – redef<strong>in</strong>ed for Swissobjectives and requirements;1. Collect detailed requirements – based on current XML proposal forproprietary Swiss standard2. Understand current R-MIM (!!! thanks to Woody Beeler)3. F<strong>in</strong>d all Swiss required elements4. Remove what not needed5. Add / change what necessary ( work through <strong>HL7</strong>)6. Run it through the process & tools• “<strong>HL7</strong> <strong>V3</strong> Lab Report Switzerland” – proposal documentprepared and distributed <strong>in</strong> German & French for review;• XML schemes to be f<strong>in</strong>alized• Work with LOINC on required codes, e.g., gestational ageNovember 2002 A. Knafel 11


<strong>HL7</strong> CH – “Lab Report <strong>V3</strong>”• Primary characteristics for Switzerland– Focus on transfer of f<strong>in</strong>d<strong>in</strong>gs from the filler (lab) to the placer– “Loosely coupled” systems– Not all patient <strong>in</strong>formation details of the placer are necessary– One XML message will be send for each patient– This message conta<strong>in</strong>s the entire service order consist<strong>in</strong>g ofmultiple positions for s<strong>in</strong>gle service/tests (i.e., multiple ORDs<strong>in</strong> one message)– All order positions will be returned <strong>in</strong> the lab report – both,pend<strong>in</strong>g and ready results will be send by the lab:“pend<strong>in</strong>g” as <strong>in</strong>tents (INT) and “ready” as events (EVN)– When multiple results exist for s<strong>in</strong>gle test order, they arecomb<strong>in</strong>ed through the act relationship: ComponentNovember 2002 A. Knafel 12


<strong>HL7</strong> CH – Lab R-MIM decisions (1/2)• Elements “Removed”– ComponentA Encounterresponsibility with<strong>in</strong> the placer system(see graphics)– ComponentB SubstanceAdm<strong>in</strong>istrationIntentcurrently not relevant – it can be added <strong>in</strong> the future– ReplacementOfresponsibility with<strong>in</strong> the placer system• Elements “Ignorable”due to 0..* optionality, low load and potential for the future(sometimes we were not sure, if we will need them <strong>in</strong> the future)– DataEnterer– PerformerNovember 2002 A. Knafel 13


<strong>HL7</strong> CH – Required R-MIM changes (1/2)• Extend EntityChoiceA <strong>in</strong> Specimen CMET for express<strong>in</strong>gownership/responsibility of the specimen.(see graphics)The ownership/responsibility shall apply to the:– Person liv<strong>in</strong>g object, e.g., <strong>in</strong> forensic medic<strong>in</strong>e for crime <strong>in</strong>vestigation, i.e. a hairfound on a dead body does not belong<strong>in</strong>g to the dead person may belong to thesuspect. The “Specimen Owner” is the dead person, the “Patient” is the suspect.– Non person liv<strong>in</strong>g object, e.g., animal ownership <strong>in</strong> veter<strong>in</strong>ary labs.– Manufactured material – it is additionally to already def<strong>in</strong>ed Manufacturer(E_Organization).• O&O committee responseThe ownership/responsibility is already established by the contextof how the Specimen CMET is used. Anyth<strong>in</strong>g beyond what isalready handled <strong>in</strong> our current ballot is outside of our scope.This means, we need to def<strong>in</strong>e the relation asA_ObservationAnnotation or at the „patient“and not the„specimen“ level.November 2002 A. Knafel 15


<strong>HL7</strong> CH – Required R-MIM changes (2/2)• The act relationship Component shall have(see graphics)type_cd


Thanks for your attention ...November 2002 A. Knafel 17

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!