Lab:V2.0.0 FHIR Lab2zorg: verschil tussen versies

Uit informatiestandaarden
Ga naar: navigatie, zoeken
(Use case: Health professional sends lab results to other health professional)
Regel 28: Regel 28:
  
 
This FHIR implementation guide assumes that systems (XIS) are able to make a connection to the right systems. It does not provide information on finding the right XIS nor does it provide information about security including authentication and authorization. Finding the right system, and security aspects of the connection are dealt with by the infrastructure. Any relevant infrastructure is expected to have a framework in place to deal with this. The only assumption/requirement for an infrastructure is that this allows RESTful FHIR based exchange as specified here.
 
This FHIR implementation guide assumes that systems (XIS) are able to make a connection to the right systems. It does not provide information on finding the right XIS nor does it provide information about security including authentication and authorization. Finding the right system, and security aspects of the connection are dealt with by the infrastructure. Any relevant infrastructure is expected to have a framework in place to deal with this. The only assumption/requirement for an infrastructure is that this allows RESTful FHIR based exchange as specified here.
 +
 +
=Actors involved=
 +
{| class="wikitable"
 +
! colspan="2" style="text-align:left;" | Persons
 +
! colspan="2" style="text-align:left;" | Systems
 +
! colspan="2" style="text-align:left;" | FHIR Capability Statements
 +
|-
 +
! style="text-align:left;" |Name
 +
! style="text-align:left;" |Description
 +
! style="text-align:left;" |Name
 +
! style="text-align:left;" |Description
 +
! style="text-align:left;" |Name
 +
! style="text-align:left;" |Description
 +
|-
 +
| rowspan="2" | Lab Professional
 +
| rowspan="2" | The user of a LIS ('''laboratory information system''')
 +
| rowspan="2" | LIS
 +
| rowspan="2" | Laboratory information system
 +
| [[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/lab2healthcare-labclientcapabilities|nictiz.fhir.nl.r4.zib2020|title=CapabilityStatement: Lab Client}}
 +
| Lab2Healthcare LIS client requirements
 +
|-
 +
| [[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/lab2healthcare-labservercapabilities|nictiz.fhir.nl.r4.zib2020|title=CapabilityStatement: Lab Server}}
 +
| Lab2Healthcare LIS server requirements
 +
|-
 +
| rowspan="2" | Healthcare professional
 +
| rowspan="2" | The user of a XIS ('''any information system''')
 +
| rowspan="2" | XIS
 +
| rowspan="2" | Healthcare information system
 +
| [[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/lab2healthcare-xisclientcapabilities|nictiz.fhir.nl.r4.zib2020|title=CapabilityStatement: XIS Client}}
 +
| Lab2Healthcare XIS client requirements
 +
|-
 +
| [[Bestand: Verwijzing.png| 20px]] {{Simplifier|http://nictiz.nl/fhir/CapabilityStatement/lab2healthcare-xisservercapabilities|nictiz.fhir.nl.r4.zib2020|title=CapabilityStatement: XIS Server}}
 +
| Lab2Healthcare XIS server requirements
 +
|}
 +
  
 
=Use case: Health professional sends order to lab and receives result from lab=
 
=Use case: Health professional sends order to lab and receives result from lab=

Versie van 23 feb 2022 om 13:17

FunctionalTechnicalFunctioneel-Technisch


1 Introduction

Go to functional design

This page describes the technical design of Lab2Zorg (Lab2Healthcare) as a subset of the Information standard lab exchange. This technical specification is implementer centric and complements the functional design. This page uses various terms as defined in the glossary (NL: Begrippenlijst). This page implements general principles applicable to FHIR as outlined by a central FHIR IG for R4. Please make sure you familiarize yourself with both the functional design and the FHIR IG for full appreciation of the context of this page.

Many laboratory results have important relationships to other observations and need to be grouped together. The FHIR specification defines several structures to do this:

  • Observation and one or more Observation.hasMember elements.
    • Each .hasMember element references another Observation and the Observation with .hasMember elements thus serves as grouper for all Observation it references. Each Observation can be accessed individually. This is useful for panels and/or batteries of tests. This is what NL-CM:13.1.3 LaboratoryTest maps into.
    • Note that while FHIR Observation also allows reference of resource types MolecularSequence | QuestionnaireResponse, there is no identified use case for that at time of writing.
    • An Observation without .hasMember elements is expected to be an individual result and has a value when one can be/is determined.
  • Observation and one or more Observation.derivedFrom elements.
    • Each .derivedFrom element references another Observation references related measurements the observation is made from. This is what NL-CM:13.1.33 RelatedResult::LaboratoryTestResult maps into.
    • Note that while FHIR Observation also allows reference of resource types DocumentReference | ImagingStudy | Media | QuestionnaireResponse | MolecularSequence, there is no identified use case for those at time of writing.
  • Observation and one or more Observation.component elements.
    • components of an Observation are not accessible individually. Whenever you access the Observation, you also access all its components. This is mostly useful when certain context is provided around the result. For lab observations this is expected to be less common. An example outside of the lab realm could be BloodPressure where systolic, diastolic, and cuff size are all in 1 Observation with 3 components.

This FHIR implementation guide assumes that systems (XIS) are able to make a connection to the right systems. It does not provide information on finding the right XIS nor does it provide information about security including authentication and authorization. Finding the right system, and security aspects of the connection are dealt with by the infrastructure. Any relevant infrastructure is expected to have a framework in place to deal with this. The only assumption/requirement for an infrastructure is that this allows RESTful FHIR based exchange as specified here.

2 Actors involved

Persons Systems FHIR Capability Statements
Name Description Name Description Name Description
Lab Professional The user of a LIS (laboratory information system) LIS Laboratory information system Verwijzing.png CapabilityStatement: Lab Client Lab2Healthcare LIS client requirements
Verwijzing.png CapabilityStatement: Lab Server Lab2Healthcare LIS server requirements
Healthcare professional The user of a XIS (any information system) XIS Healthcare information system Verwijzing.png CapabilityStatement: XIS Client Lab2Healthcare XIS client requirements
Verwijzing.png CapabilityStatement: XIS Server Lab2Healthcare XIS server requirements


3 Use case: Health professional sends order to lab and receives result from lab

TODO

4 Use case: Health professional retrieves lab results

DO

5 Use case: Health professional sends lab results to other health professional

The functional design distinguishes two use cases where lab results may be sent with something else or separate. The process of 'sending' things in FHIR works by means of a RESTful 'create' action. In principle you could a single Observation on another system using POST Observation and the appropriate Observation in the request body. When you have multiple Observations to create, you could do that for every single Observation, or by means of a Bundle with all resources. This same Bundle approach works for one Observation too.

The added benefit from a Bundle lies in having a solution for all other resources you may want to send, e.g. MedicationRequest, and referenced resources, e.g. Patient and PractitionerRole | Practitioner | Organization. Sending the Observation without the things it references would only work if the receiving server can resolve those. They should then already exist on that server, with references to them or they should be accessible on the source. Without access to the references in the Observation, the target server may not know which patient is involved or what lab this result came from.

6 Use case: Health professional reports result leading into a notification "new lab results" for subscribed healthcare professional(s)

DO