| Pages and organization | Separate display of normative content | False | Only normative content mixed with non-normative content (pages: notes, obligations, artifacts) |
| Pages and organization | Separate display of non-normative content | True | Pages: challenges.html, scenarios.html, logicalModel.html, searchform.html, background.html, downloads.html, index.html, status-mgmt.html, knownIusses.html, contributors.html, toc.html, design-choice.html, crm.html |
| Pages and organization | Presence of index page | True | Page: index.html |
| Pages and organization | Presence of toc page | True | Page: toc.html |
| Pages and organization | Presence of artifacts page | True | Page: artifacts.html |
| Pages and organization | Presence of background page | True | Page: background.html |
| Pages and organization | Presence of downloads page | True | Page: downloads.html |
| Writing and narrative | Index page starts with a patient-friendly explanation of the purpose of the IG | True | Extract (page index.html): Clinical laboratory results play an important role in diagnosis, treatment, and follow-up of patients. The availability of high quality test results, and the capacity of sharing them, is therefore essential being often the basis for clinical decision making. |
| Writing and narrative | Presence of a section that explains key information that needs to be understood prior to reading the IG | True |
- Extract (page index.html): The goal of this Implementation Guide is to define a European standard for the Laboratory Report to facilitate the harmonization among the national initiatives and prepare the ground for the European EHR eXchange Format (E-EHRxF).
- Extract (page background.html): The history of European collaboration in the health space is long, and prior to the start of the epSOS project (2008-2014), that was intended to work on the development, the pilot and the evaluation of the first cross-border eHealth service.
- Extract (page challenges.html): This page aims to summarize some of the challenges to be faced dealing with Laboratory Report in the European context, without pretending to be exhaustive.
- Extract (page design-choice.html): In brief:
A Laboratory Report is always represented by one and only one DiagnosticReport.
A DiagnosticReport shall always refers a Composition.
- Extract (page status-mgmt.html): Managing Laboratory Report statuses, as documented in Laboratory Report scenarios, could exist in several statuses. Applications consuming laboratory reports must take careful note of updated (revised) reports and ensure that retracted reports are appropriately handled.
- Extract (page obligations.html): Obligations have been added to this version of the guide only as informative material to collect feedback about their usage.
- Extract (page Bundle-BundleHepatitisPanel.html): This will be filled in by the publication tooling
- Extract (page Observation-obs-org-id1-susc-2.html): Background
This section provides key information that needs to be understood prior to reading the implementation guide.
- Extract (page DiagnosticReport-dr-lab-example.html): Background
Challenges
Design Choices
Certified reference material
- Extract (page ValueSet-lab-obsCode-loinc-eu-lab.html): Explanation of the columns that may appear on this page:
Level
A few code lists that FHIR defines are hierarchical - each code is assigned a level.
System
The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code
The code (used as the code in the resource instance)
Display
The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition
An explanation of the meaning of the concept
Comments
Additional notes about how to use the code
- Extract (page Observation-obs-gs-org1.html): Background
This section introduces the key concepts and challenges pertaining to the HL7 Europe Laboratory Report.
- Extract (page ValueSet-lab-laterality-eu-lab.html): Background
Challenges
Design Choices
Certified reference material
- Extract (page ValueSet-lab-specialty-eu-lab.html): Note 1: This value set is based on analysis of national coding practices in 8 European countries (AT, CZ, DE, FR, IE, IT, PT, SE) and agreed by involved lab experts as a common lab specialty value set.
- Extract (page ValueSet-lab-specimenType-eu-lab.html): Explanation of the columns that may appear on this page:
Level
A few code lists that FHIR defines are hierarchical - each code is assigned a level.
System
The source of the definition of the code (when the value set draws in codes defined elsewhere)
Code
The code (used as the code in the resource instance)
Display
The display (used in the display element of a Coding). If there is no display, implementers should not simply display the code, but map the concept into their application
Definition
An explanation of the meaning of the concept
Comments
Additional notes about how to use the code
- Extract (page ValueSet-lab-technique-eu-lab.html): Explanation of the columns that may appear on this page:
- Level
- System
- Code
- Display
- Definition
- Comments
|
| Writing and narrative | Presence an explanation of what "mustSupport" means for different types of implementations of the IG | True |
- Extract (page obligations.html): Obligations are a mean offered by HL7 FHIR to specify functional capabilities that defined actors MAY, SHOULD or SHALL to the data elements specified by the profiles.
|
| Writing and narrative | Presence of information on how to engage with the community | True |
- Extract (page design-choice.html): The authors are aware of the fact that this choice requires additional work to the creator, requesting to consistently record in both DiagnosticReport and Composition a set of information. However they believe, that it enables for more options for the consumer... There was a good consensus in the HL7 FHIR community for supporting this.
- Extract (page Observation-4335db48-7090-45b3-a2c2-45b45f94a67c.html): Propose a change
- Extract (page Bundle-IT-CDA2FHIR-17e2cad1-c3e3-4901-adb1-c35a0b82b883.html): Propose a change
- Extract (page Observation-obs-org-id1-susc-1.html): Propose a change
- Extract (page Observation-obs-org-id1-susc-2.html): Propose a change
- Extract (page Observation-obs-org-id1-susc-3.html): Propose a change
- Extract (page Observation-obs-org-id1-susc-4.html): Propose a change
- Extract (page ValueSet-lab-reportType-eu-lab.html): Propose a change
- Extract (page Observation-obs-anaerobic-culture.html): Propose a change
- Extract (page Observation-obs-wbc.html): Propose a change
- Extract (page Observation-obs-aerobic-culture.html): Propose a change
- Extract (page Patient-pat-lab-example.html): Propose a change
|
| Writing and narrative | Presence of an explanation of the relationship of the IG to any other guides | True |
- Extract (page index.html): This project is promoted by HL7 Europe, but realized in collaboration with several other European and national organizations and projects. The aspiration of this guide is that of being used as basis for European National Guides, the European EHRxF and - consequently - by MyHealth@EU for the EU cross-border services.
- Extract (page background.html): HL7 Europe recognized the need of promoting a Standardization activity at the European level with the purpose of: Facilitating the harmonization among the national initiatives Supporting the development of the future European-EHRxF.
- Extract (page status-mgmt.html): Please refer to the Design Choices page for details on the general approach and on how these resources are used together for the scope of this guide.
- Extract (page logicalModel.html): The European eHealth Network "GUIDELINE on the electronic exchange of health data under Cross-Border Directive 2011/24/EU Laboratory Results" - Release 1.1 is addressed to the Member States of the European Union and applies to the implementation of interoperable laboratory test result report cross-border exchange.
- Extract (page ValueSet-lab-obsCode-npu-eu-lab.html): Included into LaboratoryResultStandardEuVs
- Extract (page ValueSet-lab-obsCode-loinc-eu-lab.html): References
Included into LaboratoryResultStandardEuVs
|
| Security and privacy considerations | Presence of a section focused on security or privacy | True |
- Extract (page Bundle-SimpleChemistryResultReport.html): Security Label: N (Details: [not stated] code N)
- Extract (page Bundle-BundleHepatitisPanel.html): Security Label: N (Details: [not stated] code N)
- Extract (page Bundle-BundleLabResultMicroCultureSusc.html): Security Label: N (Details: [not stated] code N)
- Extract (page Bundle-IT-CDA2FHIR-17e2cad1-c3e3-4901-adb1-c35a0b82b883.html): Security Label: N (Details: [not stated] code N)
- Extract (page Bundle-BundleLabResultReportPOC.html): Security Label: N (Details: [not stated] code N)
- Extract (page Composition-comp-lab-example.html): confidentiality: normal
|