IHE Lab Meeting Minutes Face to Face Meeting: Difference between revisions
No edit summary |
No edit summary |
||
| Line 100: | Line 100: | ||
::* Identification of the material: The LAW messaging team had chosen container ID (SAC-3) rather than specimen ID (SPM-2), to carry the barcode identifier. Conversely, the LAB Technical Framework Vol. 2 has chosen SPM-2 for this purpose in all its profiles, although this is not enough emphasized in the current release. Hence the decision below. | ::* Identification of the material: The LAW messaging team had chosen container ID (SAC-3) rather than specimen ID (SPM-2), to carry the barcode identifier. Conversely, the LAB Technical Framework Vol. 2 has chosen SPM-2 for this purpose in all its profiles, although this is not enough emphasized in the current release. Hence the decision below. | ||
'''Decision:''' We shall write a Change Proposal to the LAB TF Vol 2, inserting the statement highlighted yellow below, after the common descriptions of the SPM and SAC segments at the end of section 3.8. The LAW transactions are expected to conform to this statement: | |||
:* The LAB Technical Framework considers in all its profiles that the specimen identifier is identical to the identifier appearing (e.g.; in bar code) on the container that holds this specimen. The proper field to carry this identifier is in all cases SPM-2 “Specimen identifier”. | |||
:* The usage of the SAC segment in the LAB TF is dedicated to carrying additional properties regarding the container (e.g.; the container location on a device). | |||
:* The condition predicates for SPM-2 and SPM-3 will be the same as SAC-3 and SAC-4 in HL7 2.5.1 chapter 13, that is: | |||
::- For a primary specimen, only SPM-2 is populated. | |||
::- For an aliquot specimen identified with a bar code, SPM-2 is the bar code of the aliquot, SPM-3 is the id of the parent specimen. | |||
::- For an aliquot specimen without bar code, SPM-2 is empty, SPM-3 shall be populated with the id of the primary specimen, and a SAC segment shall carry the specimen location as defined by HL7 2.5.1 chapter 13. | |||
:* The transactions of profiles LAW and LBL use only the 1st component of datatype EIP in fields SPM-2 and SPM-3. | |||
:* Whenever field SAC-3 is populated in a message, it shall have the same value as field SPM-2. | |||
:* Whenever field SAC-4 is populated in a message, it shall have the same value as field SPM-3. | |||
Revision as of 16:13, 13 October 2011
Back to IHE Laboratory Domain
Back to IHE Laboratory Technical Committee Page
Meeting Organization
- Host: Naomi Ishii - Hitachi High-Tech (Monday), JAHIS (Tuesday & Wednesday)
- Chair: François Macary
- Secretary: Ron Ranauro
- Daily organization & adjustments:
- Monday 19: 9 am to 5 pm, room: Hitachi coffee breaks: 10:30, 3 pm lunch: 12pm
- Tuesday 20: 9 am to 5 pm room: JAHIS coffee breaks: 10:30, 3 pm lunch: 12pm
- Wednesday 21: 9 am to 1pm room: JAHIS coffee break: 10:30 lunch: 12pm
- Meeting documents and materials are available on: ftp://ftp.ihe.net/Laboratory/Face%20to%20face%20meetings/Tokyo_2011/
Minutes (NOT COMPLETE- STILL BEING UPDATED)
1. Review of the objectives of this meeting
- A. Check LAB governance: Domain sponsors, Secretariat, LAB Representative to IHE Board
- B. LAW supplement: content review, calendar for PC release, check implementers & CAT
- C. LBL options: Discussion, content review, planning, check implementers & CAT
- D. LCC proposal: standards availability, editorial team, check implementers & CAT, planning
- E. LAB TF: Status of last ballot of Change Proposals. Planning of Release 4.0
- F. Domain Coordination Committee: procedures & docs templates, update LAB timeline
- G. Participation to connectathons: Guidance
2. Agenda Review & Adjustments: http://wiki.ihe.net/index.php?title=Lab_Domain_Agenda_19September2011
3. LAB Domain current sponsors: http://wiki.ihe.net/index.php?title=Laboratory
- Sponsors’ duties:
- Organization of face to face meetings: CAP, JAHIS, ASIP Santé - per rotation
- Organization of conference calls: CAP
- Promotion of the IHE LAB profiles
- Secretariat: CAP. John Ritter is the official secretary of IHE LAB. Ron Ranauro is taking the role for this meeting only.
4. Domain news (implementations, connectathons, showcases, success stories, perspectives …):
- A. See presentations in the meeting folder.
- B. Report from North America (Anna Orlova, Sondra Renly)
- C. Report from Japan (Yoshimi Hirasawa)
- D. Report from Europe (François Macary, Filip Migon, Alessandro Sulis, Francesca Frexia)
- E. Connectathons testing LAB profiles:
- North-America: January
- Europe: April/May
- Japan:October/November
5. IHE International &Domains Coordination:
- A. John Ritter, from CAP, is unanimously confirmed by the participants as the representative of the LAB domain to the Board of IHE International
- B. Two wiki pages to be updated from the output of this meeting:
- Domain milestones for 2011-2012 cycle: http://wiki.ihe.net/index.php?title=Domain_Milestones
- LAB timeline: http://wiki.ihe.net/index.php?title=Laboratory#Timeline_:_2011-2012_Planning_and_Development_Cycle
- C. Review templates for TF & supplements produced by the Domain Coordination Committee (deadline for review is September 30): http://wiki.ihe.net/index.php?title=Domain_Coordination_Committee#Coordination_Documents
6. Laboratory Barcode Labeling (LBL) supplement: A new optional transaction added to this profile
- A. Editorial team: Alessandro Sulis, Francesca Frexia
- B. Potential implementers: IMPECO, ISAZA, DIANOEMA, SYSTELAB, DEDALUS, … at European CAT 2012
- C. Planning: see portfolio of projects at the end of these minutes.
- D. Attention: Ensure conformance with the last DCC template for IHE supplements (vol 1, vol 2)
- Discussions:
- The event “Specimens collected” should not be part of this profile. This event exists in LTW between Order Placer and Order Filler. However it is not described explicitly enough.
- Moreover, given the flexibility of organizations that can support the 3 major use cases of LTW (1 = “specimens collected by placer”, 2 = “specimens collected by lab”, 3 = “specimens collected by 3rd party”), it appears necessary to track the “specimen collected” event with two new actors in an independent profile. Considered in a more general scope, this new profile could carry the notifications of specimen related events, such as (“collected”, “sent to lab”, “received in lab”, “broken”, “lost”, “rejected”, “arrived on station X”, “stored in bio repository”…), in any part of the workflows of lab testing (including intra-hospital, community lab testing, and inter-lab testing). The specification of the appropriate actor groupings between the two actors of this new profile and existing actors from the other profiles LTW, LBL, ILW, LDA, LAW, would enable to accommodate the various use cases and organizations for specimen workflow (collection in ward, in dedicated phlebotomy facility, at patient home, in lab, sending to another lab …). The new profile could be named Specimen Event Tracking (SET), and define two new actors: “Specimen Event Informer” and “Specimen Event Tracker”. This is a new project to add to the portfolio of IHE LAB, in wait for someone to take it and write a supplement proposal for it.
- The event “Specimens collected” is therefore not in scope of the LBL profile itself. The new option for the LBL profile must support only the trigger event “labels & containers delivered”, clearly under the responsibility of the actor “Label Broker”.
- For this event, the HL7 trigger event shall be ORC-1 = “SC” : Status change of the order to deliver the containers and attached labels, which are needed for the collection of specimens required to fulfill a lab test order group.
- The resulting status of the order shall be ORC-5 = “CM”: The order (to deliver the labels) is completed.
- Specimen centric OML^033, fits the need of this interaction.
7. Laboratory Analytical Workflow (LAW) supplement
- A. Editorial team: IICC led by IICC CTO Ed Heirman, Jean Benech from Bio Mérieux for Vol 1
- B. Potential implementers: Abbott, Roche, Orchard?, Systelab? Bio Mérieux? Siemens … at Europe CAT 2012
- C. Planning: see portfolio of projects at the end of these minutes.
- D. Attention: Ensure conformance with the last DCC template for IHE supplements (vol 1, vol 2)
- E. Technical discussions:
- Usage code “Allowed”. Need to provide a clear mapping with HL7 usage codes. To avoid the “allowed”, it is suggested to split the “usage column” in two columns, one for each sending actor: Analyzer or Analyzer Manager.
- A possible set of “Allowed” fields could be associated with an option in volume 1, which would turn them to “RE” for the Analyzer in vol 2 in case the Analyzer claims to support this option.
- The options in Vol I, section X.4 Vol I of the supplement will be modified to identify the bidirectional support for the AWOS. Broadcast and Query for AWOS are optional transactions for the Analyzer.
- The “Mandatory” code is fine provided an intial statement in Vol 2 explains its constraint, which is stronger than the HL7 usage code “R”, since it adds a receiver’s responsibility.
- 2 part “AWOS Query” transaction. The second part of the query (OML/ORL) should take place within the “AWOS Broadcast” transaction. The query transaction must specify the first part (QBP/RSP), and stress how the second part is taking place in the “AWOS Broadcast” transaction.
- Identification of equipment, model, vendor: Pre-adoption of HL7 v2.7 PRT segment linked to the OBX (resulting from discussion of Andrzej, Ed and François with HL7 OO in Cambridge Oct. 2010).
- Decision to try to build a LOINC® subset for all IVD analyzers. Project carried by Rob Bush from Orchard, and strongly supported by the Regenstrief Institute, owner of LOINC®. The decision on whether to make this subset mandatory will be taken after assessment of this subset post sufficient successful testing of the LAW profiles at connectathons in Europe, Japan and North-America.
- Units (OBX-6) will rely on UCUM terminology. Some gaps have been identified. The team will have to close them before releasing the draft for public comment. OBX-6 is conditional, the condition being that there is a result and that result is resulting from the measurement, estimate or calculation of a physical quantity.
- Order control codes: “New order”, “cancel”, “cancel as requested”, “cannot cancel”, “OK”: A subset from the common list selected by the LAB Technical Framework , Vol. 2 section 3.5
- The LAW supplement removes effectively the transaction LAB-23 and the actor “Analyzer” from the LDA profile. This must be explicitly stated as editing instructions in the LAW supplement.
- “UNICODE UTF-8” will be used as the character set for LAW message transmissions. This value will be set in MSH-18.
- Enhanced acknowledgment mode, as discussed during the Sept 2010 face-to-face meeting, will be implemented for the LAW messaging. Only one acknowledgement will be sent (either application or accept). To support this decision, MSH-15 will be set to “ER” and MSH-16 will be set to “AL”.
- Identification of the material: The LAW messaging team had chosen container ID (SAC-3) rather than specimen ID (SPM-2), to carry the barcode identifier. Conversely, the LAB Technical Framework Vol. 2 has chosen SPM-2 for this purpose in all its profiles, although this is not enough emphasized in the current release. Hence the decision below.
Decision: We shall write a Change Proposal to the LAB TF Vol 2, inserting the statement highlighted yellow below, after the common descriptions of the SPM and SAC segments at the end of section 3.8. The LAW transactions are expected to conform to this statement:
- The LAB Technical Framework considers in all its profiles that the specimen identifier is identical to the identifier appearing (e.g.; in bar code) on the container that holds this specimen. The proper field to carry this identifier is in all cases SPM-2 “Specimen identifier”.
- The usage of the SAC segment in the LAB TF is dedicated to carrying additional properties regarding the container (e.g.; the container location on a device).
- The condition predicates for SPM-2 and SPM-3 will be the same as SAC-3 and SAC-4 in HL7 2.5.1 chapter 13, that is:
- - For a primary specimen, only SPM-2 is populated.
- - For an aliquot specimen identified with a bar code, SPM-2 is the bar code of the aliquot, SPM-3 is the id of the parent specimen.
- - For an aliquot specimen without bar code, SPM-2 is empty, SPM-3 shall be populated with the id of the primary specimen, and a SAC segment shall carry the specimen location as defined by HL7 2.5.1 chapter 13.
- The transactions of profiles LAW and LBL use only the 1st component of datatype EIP in fields SPM-2 and SPM-3.
- Whenever field SAC-3 is populated in a message, it shall have the same value as field SPM-2.
- Whenever field SAC-4 is populated in a message, it shall have the same value as field SPM-3.
Attendees
- (*) participating online
| Name | Organization |
|---|---|
| Filip Migom | MIPS |
| Anna Orlova | PHDSC |
| Jean Benech (editor for LAW vol 1) | Bio Mérieux |
| Ed Heierman (project lead for LAW) | Abbott Diagnostics |
| Ron Ranauro (LAB secretary for the meeting) | CAP |
| Shigeo Hasegawa | Beckman Coulter |
| Hiroyoshi Okada (chair of IHE LAB Japan) | ITEC Hankyu-Hanshin |
| Nobuyuki Chiba | A&T Corporation |
| Tsuyashi Kawata | ITEC Hankyu-Hanshin |
| Shinishi Watanabe | A&T Corporation |
| Francesca Frexia (editor for LBL extension) | CRS4 |
| Alessandro Sulis(editor for LBL extension) | CRS4 |
| Naomi Ishii (Host) | Hitachi High-Tec |
| Ken Iguchi | Osaka Medical College |
| Jim Harrison(*) (project lead for LCC) | CAP |
| Mayu Nagao | A&T Corporation |
| Osamu Yamada (LAB Planning Cochair) | Okazaki City Hospital |
| François Macary (LAB Planning Cochair) | ASIP Santé |
| Yoshimi Hirasawa (LAB Technical Cochair) | Techno Medica |
| Sondra Renly(*) (LAB Technical Cochair) | IBM |
| John Ritter (*) | CAP |