CH LAB-Order (R4)
2.0.0 - ci-build Switzerland flag

CH LAB-Order (R4), published by HL7 Switzerland. This guide is not an authorized publication; it is the continuous build for version 2.0.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/hl7ch/ch-lab-order/ and changes regularly. See the Directory of published versions

Changelog

All significant changes to this FHIR implementation guide will be documented on this page.

Open Issues for STU 3

  • Issue#296 Add task resource to enable workflow communication

  • Issue #260 Using Laboratory Catalogue

  • Issue #72 Relation between Tests and Specimens my be needed. The relation should be established by a test-specific PlanDefinition as extension specimenRequested, which points to the test-specific SpecimenDefinition. The test-specific PlanDefinition and SpecimenDefinitin should be provided by a LabCatalog/Compendium. So the Lab Organization can independently define their tests with all the needed preanalytic conditions.

  • Issue #128 Mapping reasonCode und reasonReference from Q to SR

  • Issue #127 Mapping Questionnaire code to Service Request code

STU 2 Ballot

  • Isssue # 284 Home - IG Fragments (Safety Considerations) (Patrick Jolo eHealth Suisse) - changed

  • Isssue # 282 Examples needed that indicate request of analyses and linked information (Corina von Känel) - Example added

  • Isssue # 281 Use Cases in German: use case 10 a specialised case of use case 2? (Emmanuel Eschmann, CISTEC) - All Use Cases and translations refactored because of making the order using Questionnaire and QuestionnaireResponse as option

  • Isssue # 280 FHIR IGs must not have a TODO to be eligible for FMM Level 3 (Emmanuel Eschmann, CISTEC) - open TODOs resolved

  • Isssue # 279 Use Cases in German: Profile for use case 2? (Emmanuel Eschmann, CISTEC) - All Use Cases and translations refactored because of making the order using Questionnaire and QuestionnaireResponse as option

  • Isssue # 278 Mismatch between use case 2 in English and in German (Emmanuel Eschmann, CISTEC) - All Use Cases and translations refactored because of making the order using Questionnaire and QuestionnaireResponse as option

  • Isssue # 277 Management Summary Change - rewording (Corina von Känel, CISTEC AG) - Management summary text has been modified.

  • Isssue # 276 Ordering of Containers, Blood Pressure instruments should not be covered by lab order (Corina von Känel, CISTEC AG) - Ordering of non laboratory sample measurments is no more part of the IG

  • Isssue # 275 Home: Typos (Michaela Ziegler, ahdis ag) - Typos fixed

  • Isssue # 274 CH LAB-ORDER Document Profile: Spelling (Michaela Ziegler, ahdis ag) - Spelling is unfied

  • Isssue # 272 Case Studies in German (Gabriel Hess, BFH I4MI) #272 - Links fixed

  • Issue #253 shift license to CC0 1.0 Universal (CC0 1.0) - Switched to CC

Follow up of changes in CH-orf

Changed / Updated

  • Issue #132 Try to build a Questionnaire with a general part and 6 specific parts: Questionnaire Specification

  • Issue #88 The pre-analytical conditions and any limitations are specified in the laboratory catalogue. These include, for example, the fasting of the patient, the type of sample container, the storage period and temperature of the sample, the reasons for rejection, etc. In addition, the costs of Vitamim D determination are only covered by health insurance in certain situations, e.g. rickets, osteoporosis, etc.

  • Issue #87 Relations between Specimens and Tests. Refer to Issue #72

  • Issue #80 User should be able to select analyses or analyse panels from a Laboratory Catalog. The applies to Specimens

  • Issue #79 Pick desired Analyses and Specimens from am Catalog

  • Issue #78 Test to be performed is missing in ServiceRequest.code

  • Issue #77 Pathology Order: Case Study and Instance is added: Case study 6: Suspected Melanoma, order for histopathology examination
  • Issue #89: Case Study 0-generic has been deleted.
  • Issue #86: Add Term ‘Nachverordnung’ in ChLabOrderServiceRequestCategories codesystem
  • Issue #85: Remove SR of Vital Monitoring Devices; should be realized under a separate IG
  • Issue #84: The Resource Service Request provides that reasonCode and/or a reasonReference can be added to the job as Condition Observation Diagnostic Report DocumentReference; the descrption of UC 7 has been completed

  • Issue #82: Previous lab results or images can be easily requested by phone. However, if a previous order can still be found in the system, the associated results can be requested easily and precisely by adjusting the value of ServiceRequest.categories accordingly.

  • Issue #81: Laborder without Q / QR: By adopting from the change in ORF, proposal 2 from Emmanuel and the UC around “lab orders without Forms/ Q QR” comes to fruition:
  • Issue #76: Want’s to add a Reason for Order: We have reasonReference reasonCode and reasonCode.text in SR for further informations, has zu be mapped Q to SR; see issue #128 above
  • Issue #75: resolved in ORF: Practitioner and PractitionerRole may have GLN and ZSR as Identifier, the same for ReceiverCopies, has to be resolved in ORF too in a STU 2
  • Issue #74: AHVN13 as Patient Identifier: The use of the AHVN13 is regulated in Art. 5 EPDG. It can be used for: query of the patient identification number at the central clearing office ZAS correct assignment of the patient identification number. In principle, several identifiers are possible for the patient. BUT: It is forbidden to store the AHVN13 permanently. Thus, the use of AHVN13 as a patient identifier is not possible.
  • Issue #73: resolved, see issue #75 above
  • Issue #71: Missing insurance Information: resolved, see http://fhir.ch/ig/ch-core/StructureDefinition/ch-core-organization-epr
  • Issue #65: addition form conformance
  • Issue #64: The fields order.title, order.type and order.category are readonly in the CH ORF Questionnaire, so the same in Laborder
  • Issue #62: Document Profile is missing: added

Issues resolved without amendment

usecases-german.md

  • Replace: Use Case 2: Verordnung zusätzlicher Untersuchungen der gleichen Probe with Use Case 2: Laborverordnung ohne Verwendung von Questionnaire und QuestionnaireResponse

  • Add example: Use Case 6: Vorschlag von zusätzlichen oder alternativen Untersuchungen durch den Laborarzt (Auftragsempfänger, receiver)

  • Modify: Use Case 4: Anfordern von vorhandenen Laborresultaten und Bildern.

  • Remove: Use Case 9: Anfordern von Monitoring-Untersuchungen (nicht empfohlen)