0.1.7 - ci-build
0.1.7 - ci-build
EgdeEHG_IG - Local Development build (v0.1.7). See the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.
| Egde Health Gateway FHIR facade general capabity statement - TODO modify this UK example |
Gateway supports TBD. |
These define constraints on FHIR resources for systems conforming to this implementation guide.
| CareTeam - Egde Health Gateway - profile |
Egde Health Gateway care team profile |
| DiagnosticReport - Egde Health Gateway - profile |
DiagnosticReport for Egde Health Gateway FHIR APIs |
| Goal - Egde Health Gateway - profile |
Egde Health Gateway Goal profile |
| Organization - Egde Health Gateway - profile for international use |
Egde Health Gateway organization profile for organisations that are not officially registered in the Norwegian Health Network or are outside Norway. An example could be for a sample that is sent to a lab outside Norway. Note: always use officially registered entities where possible. |
| Consent - Egde Health Gateway - Profile |
Resource containing the Consent details |
| DocumentReference - Egde Health Gateway - profile |
Egde Health Gateway DocumentReference profile |
| Organization - Egde Health Gateway - profile for domestic use |
Egde Health Gateway organization profile Egde Health Gateway organization profile for organisations that are officially registered in the Norwegian Health Network. |
| Patient - Egde Health Gateway - profile for Norwegian patients |
Based on Basisprofil for Norwegian Patient information. Defined by The Norwegian Directorate of eHealth and HL7 Norway. Should be used as a basis for further profiling in use-cases where specific identity information is needed. The basis profile is open, but derived profiles should close down the information elements according to specification relevant to the use-case. |
| Practitioner - Egde Health Gateway - profile for Norwegian practitioners |
Based on Basisprofil for Norwegian Practitioner information. Defined by The Norwegian Directorate of eHealth and HL7 Norway. Should be used as a basis for further profiling in use-cases where specific identity information is needed. The basis profile is open, but derived profiles should close down the information elements according to specification relevant to the use-case. |
| Observation - Egde Health Gateway - profile |
Egde Health Gateway observations - possibly never used at EHG level |
| QuestionnaireResponse - Egde Health Gateway - profile |
QuestionnaireResponse - Egde Health Gateway - profile |
| ServiceRequest - Egde Health Gateway - profile |
Egde Health Gateway DocumentReference profile |
| Specimen - Egde Health Gateway - profile |
Egde Health Gateway Specimen for reference by Observations |
These define constraints on FHIR data types for systems conforming to this implementation guide.
| DocumentReference - Egde Health Gateway - profile |
Egde Health Gateway DocumentReference profile |
| Address - Egde Health Gateway - profile for domestic use |
Egde Health Gateway address profile Egde Health Gateway organization profile for organisations that are officially registered in the Norwegian Health Network. |
These define sets of codes used by systems conforming to this implementation guide.
| Care Team role |
Care team role codes from Snomed CT describing types of practitioners and groups |
| Consent codes from Loinc and Snomed-ct |
Consent codes from Loinc and Snomed-ct |
| Volven 9602 Dokumenttyper |
Alllowed codes from Volven 9602 Dokumenttyper |
| Organisatorisk betegnelse |
Alllowed codes from Volven 8624 Organisatorisk betegnelse |
| Organization type |
Organization types for international use |
| Specimen types |
Alllowed codes from https://terminology.hl7.org/3.1.0/ValueSet-v2-0487.html |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.
| Lab01 |
Organization details for the lab based on its internal reference & name, not official IDs |
| CLI1 |
Organization details for the clinic based on its enhets org number not Her-ID |
| EHGConsentMotivertHymnePrivacy |
Example of a privacy positive consent for a patient |
| EHGConsentMotivertHymneResearch |
Example of a privacy negative consent for a patient |
| MotivertHymne |
Norway Patient Motivert Hymne taken from no-basis FSH instances |
| DemotivertHymne |
Patient Demotivert Hymne taken from no-basis FSH instances |
| LineDanser |
Norway Patient Line Danser taken from no-basis FSH instances |
| PractitionerHansHansen |
Example of a norway practitioner Kumar Magnar with both HPR and FNR ids |
| MotivertSang |
Patient Motivert Sang taken from no-basis FSH instances |
| PractitionerLarsLarsen |
Example of a Norway practitioner Kumar Magnar with both HPR and FNR ids |
| PractitionerMonsMonsen |
Example of a Norway practitioner Kumar Magnar with both HPR and FNR ids |
| DemotivertSang |
Patient DemotivertSang taken from no-basis FSH instances |