0.1.2 - ci-build
0.1.2 - ci-build
EgdeTigeni_IG - Local Development build (v0.1.2). See the Directory of published versions
| Official URL: http://www.egde.no/ImplementationGuide/fhir.egdetigeni | Version: 0.1.2 | |||
| Draft as of 2023-02-24 | Computable Name: EgdeTigeni_IG | |||
This document is a FHIR IG for Tigeni Symbio defining the FHIR facade for standard data interchange.
The API is for a Patient app where the patient context is set using the Smart App Launch framework.
A client application will receive a Bundle containing DiagnosticReport(s) and enclosed Specimen(s) and Observation(s).
The FHIR Facade API exposes the following resources and operations:
DiagnosticReport uses the profile TigeniDiagnosticReport based on EHGDiagnosticReport. See section: Artifacts.
The laboratory generates a report from the patient’s blood sample and analysed into diag report here – the Loinc codes will specific the type of analyse – in this case blood analysis.
When this endpoint is called with an {Id}, the FHIR api will make a call to the Tigeni Api for resource ResultReport/{id}. If the patient reference in the ResultReport matches the authentication-context the data will be mapped to FHIR format.
The DiagnosticReport resource contains references to the patient’s input - Specimen resources and to the laboratory output - Observation resources.
Specimen uses the profile TigeniSpecimen based on EHGSpecimen. See section: Artifacts.
Coding for Specimens comes from Volven: Prøvemateriale (OID=8351).
Observation uses the profile TigeniObservation based on EHGObservation. See section: Artifacts.
Coding for Observations comes from Volven: Norsk laboratoriekodeverk (OID=7280) and Volven: Tekstlige resultatverdier for mikrobiologiske svar (OID=8340).
The Patient uses the Egde Health Gateway Norwegian Patient profile. This is based on the Norwegian no-basis-patient profile and the Patient ID must be either FNR (fødselsnummer) or DNR (D-nummer).
SMART Apps Launch Framework is used as an authentication method for allowing other healthcare systems access to your health data through a web API. It’s based on OIDC and requires the support for a launch context that defines the scope of access to resources.
The following launch context will be used:
Non-Norwegian patients will be provided at a later date.
The Practitioner uses the Egde Health Gateway Practitioner profile. This is based on the Norwegian no-basis-practitioner profile. The practitioner ID must be either FNR (fødselsnummer) or HPR (helsepersonelnummer).
The Organization uses the Egde Health Gateway Organization Norway profile. The Organization is based on the Norwegian no-basis-organization profile. An ID is not enforced but Norwegian clinics are identified by name and organization ID from the Enhetsregisteriet (ENH).
It has will have a fixed type of organization derived from the Volven code: OrganisatoriskBetegnelse.
Non-norwegian organizations will be supported at a later date.
The Consent uses the Egde Health Gateway Consent profile. Consent resource for Opt-in and Opt-out are available. The only consent type supported is LOINC code #59284-0 “Patient Consent”.