CH LAB-Order (R4)
2.0.0 - trial-use
This page is part of the CH LAB-Order (R4) (v2.0.0: STU 2) based on FHIR (HL7® FHIR® Standard) R4. This is the current published version in its permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions
All significant changes to this FHIR implementation guide will be documented on this page.
Issue #314 Profile : ChLabOrderMedication -> Parent: Medication, Profile: MedicationStatement -> CHCoreCHCoreMedicationStatement, Profile: ChLabOrderDiagnosisCondition -> Parent: Condition
Issue #313 ch.fhir.ig.ch-lab-order#2.0.0-ballot /terminology.html – replaced status = #draft with status = #active in all occurrencies
Issue #312 Rename ChLabOrderLabSpecialties to ChLabOrderLabStudyTypes, change title to “Laboratory Study Types”. Translate all Titles of ValueSets to english.
Issue #311 removed from Aliases.fsh: Alias: $documentEntryClassCode, Alias: $documentEntryTypeCode
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 SpecimenDefinition 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
Issue #284 Home - IG Fragments (Safety Considerations) (Patrick Jolo eHealth Suisse) - changed
Issue #282 Examples needed that indicate request of analyses and linked information (Corina von Känel) - Example added
Issue #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
Issue #280 FHIR IGs must not have a TODO to be eligible for FMM Level 3 (Emmanuel Eschmann, CISTEC) - open TODOs resolved
Issue #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
Issue #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
Issue #277 Management Summary Change - rewording (Corina von Känel, CISTEC AG) - Management summary text has been modified.
Issue #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 measurements is no more part of the IG
Issue #275 Home: Typos (Michaela Ziegler, ahdis ag) - Typos fixed
Issue #274 CH LAB-ORDER Document Profile: Spelling (Michaela Ziegler, ahdis ag) - Spelling is unified
Issue #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
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 Vitamin 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 #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.