MedMij:V2017.04 FHIR LaboratoryResults: verschil tussen versies

Uit informatiestandaarden
Naar navigatie springen Naar zoeken springen
Ardon Toonstra (overleg | bijdragen)
Geen bewerkingssamenvatting
Ardon Toonstra (overleg | bijdragen)
Geen bewerkingssamenvatting
Regel 1: Regel 1:
{{#customtitle:MedMij FHIR use case LaboratoryResults, publication 2017.04}}
{{#customtitle:MedMij FHIR use case LaboratoryResults}}
 
{{IssueBox|This page is a working page.}}


[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]
[[Bestand:MedMij2.png |link=https://www.medmij.nl/|rechts|Naar medmij.nl]]

Versie van 18 dec 2017 11:54

{{#customtitle:MedMij FHIR use case LaboratoryResults}}

Naar medmij.nl
Naar medmij.nl
Medication process
Medication process
Afspraken-Functioneel-TechnischAfsprakenstelselFunctioneelTechnisch

Introduction

Actors involved

Use case: retrieve laboratory results

Introduction

The retrieve laboratory results transaction is used by the PHR to retrieve a laboratory results from a XIS.

Actors

Transaction group Transaction System role code Actor Role
Retrieve Laboratory Results(PULL) Retrieve laboratory results request LAB-LRR-FHIR Patient (using a PHR) Request laboratory results from the XIS
Retrieve laboratory results response LAB-LRB-FHIR Healthcare professional (using a XIS) Serves laboratory results to the PHR

Invocations

PHR: request message

Trigger Events

Message Semantics

Expected Actions

XIS: response message

Trigger Events

Message Semantics

Resource content
ZIB name NL ZIB name EN FHIR Resource URL profile Reference to section
Patient Patient Patient http://fhir.nl/fhir/StructureDefinition/nl-core-patient Patient
Zorgverlener HealthProfessional Practitioner http://fhir.nl/fhir/StructureDefinition/nl-core-practitioner HealthProfessional
Zorgaanbieder HealthcareProvider Organization http://fhir.nl/fhir/StructureDefinition/nl-core-organization HealthcareProvider

Expected Actions

Interactions, operations, search parameters

Interactions

The following logical interactions are needed for the retrieve medication overview transaction:

Operations

No operations are defined or needed for this transaction.

Search parameters

The following search parameter type needs to be supported for this transaction.

Search parameter types:

Examples