diff --git a/input/ignoreWarnings.txt b/input/ignoreWarnings.txt index ffd45936..9b2bdcb7 100644 --- a/input/ignoreWarnings.txt +++ b/input/ignoreWarnings.txt @@ -1 +1,16 @@ == Suppressed Messages == + +# Different display values (language) +Der Displayname% + +# External CodeSystem +A definition for CodeSystem 'urn:oid:2.51.1.1' could not be found, so the code cannot be validated +A definition for CodeSystem 'urn:oid:2.16.756.5.30.2.6.1' could not be found, so the code cannot be validated +A definition for CodeSystem 'https://medcodesearch.ch/de/AL/laboratory_analyses' could not be found, so the code cannot be validated +A definition for CodeSystem 'https://testdirectory.questdiagnostics.com/' could not be found, so the code cannot be validated + +# No OIDs at the moment +This resource could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root) + +# Reference to draft CodeSystem +Reference to draft CodeSystem% diff --git a/input/pagecontent/changelog.md b/input/pagecontent/changelog.md index 0c52a6e0..89c69d73 100644 --- a/input/pagecontent/changelog.md +++ b/input/pagecontent/changelog.md @@ -2,22 +2,22 @@ All significant changes to this FHIR implementation guide will be documented on this page. -#### Open Issues for STU 3 +### Open Issues for STU 3 -* [Issue#314](https://github.com/hl7ch/ch-lab-order/issues/314) Profile : ChLabOrderMedication -> Parent: Medication, Profile: MedicationStatement -> CHCoreCHCoreMedicationStatement, Profile: ChLabOrderDiagnosisCondition -> Parent: Condition +* [Issue #314](https://github.com/hl7ch/ch-lab-order/issues/314) Profile : ChLabOrderMedication -> Parent: Medication, Profile: MedicationStatement -> CHCoreCHCoreMedicationStatement, Profile: ChLabOrderDiagnosisCondition -> Parent: Condition -* [Issue#313](https://github.com/hl7ch/ch-lab-order/issues/313) ch.fhir.ig.ch-lab-order#2.0.0-ballot /terminology.html -- replaced status = #draft with status = #active in all occurrencies +* [Issue #313](https://github.com/hl7ch/ch-lab-order/issues/313) ch.fhir.ig.ch-lab-order#2.0.0-ballot /terminology.html -- replaced status = #draft with status = #active in all occurrencies -* [Issue#312](https://github.com/hl7ch/ch-lab-order/issues/312) Rename ChLabOrderLabSpecialies to ChLabOrderLabStudyTypes, change title to "Laboratory Study Types". Translate all Titles of ValueSets to english. +* [Issue #312](https://github.com/hl7ch/ch-lab-order/issues/312) Rename ChLabOrderLabSpecialties to ChLabOrderLabStudyTypes, change title to "Laboratory Study Types". Translate all Titles of ValueSets to english. -* [Issue#311](https://github.com/hl7ch/ch-lab-order/issues/311) removed from Aliases.fsh: +* [Issue #311](https://github.com/hl7ch/ch-lab-order/issues/311) removed from Aliases.fsh: Alias: $documentEntryClassCode, Alias: $documentEntryTypeCode -* [Issue#296](https://github.com/hl7ch/ch-lab-order/issues/296) Add task resource to enable workflow communication +* [Issue #296](https://github.com/hl7ch/ch-lab-order/issues/296) Add task resource to enable workflow communication * [Issue #260](https://github.com/hl7ch/ch-lab-order/issues/260) Using Laboratory Catalogue -* [Issue #72](https://github.com/hl7ch/ch-lab-order/issues/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 #72](https://github.com/hl7ch/ch-lab-order/issues/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](https://github.com/hl7ch/ch-lab-order/issues/128) Mapping reasonCode und reasonReference from Q to SR @@ -25,31 +25,31 @@ Alias: $documentEntryClassCode, Alias: $documentEntryTypeCode ### STU 2 Ballot -* [Isssue # 284](https://github.com/hl7ch/ch-lab-order/issues/284) Home - IG Fragments (Safety Considerations) (Patrick Jolo eHealth Suisse) - changed +* [Issue #284](https://github.com/hl7ch/ch-lab-order/issues/284) Home - IG Fragments (Safety Considerations) (Patrick Jolo eHealth Suisse) - changed -* [Isssue # 282](https://github.com/hl7ch/ch-lab-order/issues/282) Examples needed that indicate request of analyses and linked information (Corina von Känel) - Example added +* [Issue #282](https://github.com/hl7ch/ch-lab-order/issues/282) Examples needed that indicate request of analyses and linked information (Corina von Känel) - Example added -* [Isssue # 281](https://github.com/hl7ch/ch-lab-order/issues/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 #281](https://github.com/hl7ch/ch-lab-order/issues/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](https://github.com/hl7ch/ch-lab-order/issues/280) FHIR IGs must not have a TODO to be eligible for FMM Level 3 (Emmanuel Eschmann, CISTEC) - open TODOs resolved +* [Issue #280](https://github.com/hl7ch/ch-lab-order/issues/280) FHIR IGs must not have a TODO to be eligible for FMM Level 3 (Emmanuel Eschmann, CISTEC) - open TODOs resolved -* [Isssue # 279](https://github.com/hl7ch/ch-lab-order/issues/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 #279](https://github.com/hl7ch/ch-lab-order/issues/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](https://github.com/hl7ch/ch-lab-order/issues/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 #278](https://github.com/hl7ch/ch-lab-order/issues/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](https://github.com/hl7ch/ch-lab-order/issues/277) Management Summary Change - rewording (Corina von Känel, CISTEC AG) - Management summary text has been modified. +* [Issue #277](https://github.com/hl7ch/ch-lab-order/issues/277) Management Summary Change - rewording (Corina von Känel, CISTEC AG) - Management summary text has been modified. -* [Isssue # 276](https://github.com/hl7ch/ch-lab-order/issues/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 +* [Issue #276](https://github.com/hl7ch/ch-lab-order/issues/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 -* [Isssue # 275](https://github.com/hl7ch/ch-lab-order/issues/275) Home: Typos (Michaela Ziegler, ahdis ag) - Typos fixed +* [Issue #275](https://github.com/hl7ch/ch-lab-order/issues/275) Home: Typos (Michaela Ziegler, ahdis ag) - Typos fixed -* [Isssue # 274](https://github.com/hl7ch/ch-lab-order/issues/274) CH LAB-ORDER Document Profile: Spelling (Michaela Ziegler, ahdis ag) - Spelling is unfied +* [Issue #274](https://github.com/hl7ch/ch-lab-order/issues/274) CH LAB-ORDER Document Profile: Spelling (Michaela Ziegler, ahdis ag) - Spelling is unified -* [Isssue # 272](https://github.com/hl7ch/ch-lab-order/issues/272) Case Studies in German (Gabriel Hess, BFH I4MI) #272 - Links fixed +* [Issue #272](https://github.com/hl7ch/ch-lab-order/issues/272) Case Studies in German (Gabriel Hess, BFH I4MI) #272 - Links fixed * [Issue #253](https://github.com/hl7ch/ch-lab-order/issues/253) shift license to CC0 1.0 Universal (CC0 1.0) - Switched to CC -#### Follow up of changes in CH-orf +#### Follow up of changes in CH ORF * [Change Log CH-ORF](http://build.fhir.org/ig/hl7ch/ch-orf/changelog.html): @@ -57,7 +57,7 @@ Alias: $documentEntryClassCode, Alias: $documentEntryTypeCode * [Issue #132](https://github.com/hl7ch/ch-lab-order/issues/132) Try to build a Questionnaire with a general part and 6 specific parts: [Questionnaire Specification](http://build.fhir.org/ig/hl7ch/ch-lab-order/Questionnaire-LabOrder-form.html) -* [Issue #88](https://github.com/hl7ch/ch-lab-order/issues/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 #88](https://github.com/hl7ch/ch-lab-order/issues/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](https://github.com/hl7ch/ch-lab-order/issues/87) Relations between Specimens and Tests. Refer to [Issue #72](https://github.com/hl7ch/ch-lab-order/issues/72) @@ -75,7 +75,7 @@ Alias: $documentEntryClassCode, Alias: $documentEntryTypeCode * 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:](https://github.com/hl7ch/ch-rad-order/issues/18#issue-1001931518) -* 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 #76: Want's to add a Reason for Order: We have reasonReference reasonCode and reasonCode.text in SR for further information, 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. @@ -87,7 +87,7 @@ correct assignment of the patient identification number. In principle, several i #### Issues resolved without amendment -* removed not used ValuSets +* removed not used ValueSets * put serviceRequest.categories into ChLabOrderSR, replace it's value with fixed value 'Laboratory procedure (procedure)' for all ServiceRequests. * replace in casestudies parent ChOrfServiceRequest with ChLabOrderSR * reset dependencies ch.fhir.ig.ch-orf: current to 2.0.1 diff --git a/input/pagecontent/index.md b/input/pagecontent/index.md index 1af72e13..600b5086 100644 --- a/input/pagecontent/index.md +++ b/input/pagecontent/index.md @@ -1,11 +1,5 @@ -
- ### HL7 Swiss FHIR Implementation Guide for generic laboratory orders #### Laboratory Order with Service Request @@ -22,9 +16,15 @@ There is another use case in which the commissioning laboratory provides the cli You can download this Implementation Guide in [NPM-format](https://confluence.hl7.org/display/FHIR/NPM+Package+Specification) from [here](https://fhir.ch/ig/ch-lab-order/package.tgz). + + ### Foundation -Data exchange with different information systems (practice, hospital, laboratory) quickly becomes confusing due to proprietary solutions (n:m cardinality). Therefore, the question arises whether a standardised order interface is the more favourable solution in the long run. +Data exchange with different information systems (practice, hospital, laboratory) quickly becomes confusing due to proprietary solutions (n:m cardinality). Therefore, the question arises whether a standardized order interface is the more favorable solution in the long run. #### Laboratory order with Service Request @@ -34,7 +34,7 @@ The ServiceRequest may instantiate an ActivityDefinition, a coded procedure to e #### Laboratory order with Service Request and Form -The lab order can optionally and in addition to the ServiceRequest contain forms as resources, which in this context are called Questionnaire and QuestionnairResponse. The structure of these forms is [based on ORF](http://fhir.ch/ig/ch-orf/ImplementationGuide/ch.fhir.ig.ch-orf). This allows the data for the laboratory order to be placed in a structured way. +The lab order can optionally and in addition to the ServiceRequest contain forms as resources, which in this context are called Questionnaire and QuestionnaireResponse. The structure of these forms is [based on ORF](http://fhir.ch/ig/ch-orf/ImplementationGuide/ch.fhir.ig.ch-orf). This allows the data for the laboratory order to be placed in a structured way. ### Requirements @@ -51,13 +51,13 @@ The lab-order should define the structure of the order details so it can be used * Information for the sample taking should be available for the person preparing the taking of blood. - * A numbering system should be supported, so that relabeling at the laboratory can be limited (eg. practitionar number + number-range). + * A numbering system should be supported, so that relabeling at the laboratory can be limited (eg. practitioner number + number-range). 5. The electronic order should be able to handle the request of analyses for samples that were sent at an earlier point of time. 6. The electronic order should receive updates on the process of the laboratory analyses: as sample received in laboratory, first results available, report finished [Domain of Lab-Report]. - * The status of the order at the practitionor site should be supported as well: new order, replaced order (enhanced or partly deleted), printed sample lables, documentation of blood take (additional Information as urine volume and Date and Time of withdrawl of blood). + * The status of the order at the practitioner site should be supported as well: new order, replaced order (enhanced or partly deleted), printed sample labels, documentation of blood take (additional Information as urine volume and Date and Time of withdrawal of blood). ### Six Case studies with examples for the Order Document @@ -65,7 +65,7 @@ Using concrete case studies, we have created six everyday examples of documents ### Copyright -This artefact includes content from SNOMED Clinical Terms® (SNOMED CT®) which is copyright of the International Health Terminology Standards Development Organisation (IHTSDO). Implementers of these artefacts must have the appropriate SNOMED CT Affiliate license - for more information contact