HL7® Austria FHIR® Core Implementation Guide
1.1.0 - STU2

Artifacts Summary

This page provides a list of the FHIR artifacts defined as part of this implementation guide.

Structures: Resource Profiles

These define constraints on FHIR resources for systems conforming to this implementation guide.

HL7® AT Core Patient Profile

HL7® Austria FHIR® Core Profile for patient data in Austria. The HL7® AT Core Patient is based upon the core FHIR® Patient Resource and designed to meet the applicable patient demographic data elements in Austria. It identifies which core elements, extensions, vocabularies and value sets SHALL be present in the resource when using this profile. Note, this extension represents the common structure of Patient information within Austrian information systems.

HL7® AT Core ValueSet Profile

HL7® Austria FHIR® Core Profile for valuesets in Austria. The HL7® AT Core ValueSet is based upon the core FHIR® ValueSet Resource and defines the use of the OID extension.

Structures: Data Type Profiles

These define constraints on FHIR data types for systems conforming to this implementation guide.

HL7® AT Core Address Profile

HL7® Austria FHIR® Core Profile for address data in Austria. Note, this extension represents the common structure of address information within Austrian information systems. This extension does not restrict the documented information to Austrian adresses. Address information that does not fit into the given structure may be captured by Address Additional Information.

Structures: Extension Definitions

These define constraints on FHIR data types for systems conforming to this implementation guide.

Address Additional Information

HL7® Austria FHIR® Core Extension for the additional information part of the Austrian address.

Patient Religion

HL7® Austria FHIR® Core Extension for the religion (registered in Austria) of a patient. The extension is used to encode the religious confession of a patient (only confessions registered in Austria). Furthermore, it uses the official HL7 AT CodeSystem for religion and is therefore aligned with the ELGA ValueSet, respectively.

System OID

HL7® Austria FHIR® Core Extension for the capturing of OID in ValueSets to reference the CodeSystem they come from. The extension is used to document the OID of the system of a code referenced in a ValueSet, to align FHIR with the HL7 Austria CDA document guidelines.

Terminology: Value Sets

These define sets of codes used by systems conforming to this implementation guide.

at-elga-vs-countryCodes

Value Set for ISO 3166-1 alpha 3 used in ELGA. Also accessible on Termpub - ValueSet - ELGA Ländercodes.

at-elga-vs-religion

Set of religious affiliations to be used in ELGA. It is preferred to use entries of the first level hierachy (1-L). Also accessible on Termpub - ValueSet - ELGA ReligiousAffiliation.

Terminology: Code Systems

These define new code systems used by systems conforming to this implementation guide.

at-core-cs-iso-3166-1-alpha-3

ISO code system for country codes with 3 letters. Also accessible on Termpub - CodeSystem - ISO 3166-1 alpha 3.

at-core-cs-religion

Code system for the religions and faith communities in Austria. Also accessible on Termpub - CodeSystem - HL7 AT ReligionAustria.

Example: Example Instances

These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like.

HL7ATCorePatientExample01

Example for the usage of the HL7 AT Core Patient Profile

HL7ATCorePatientExample02-deceasedTime

Example with deceasedTime for the usage of the HL7 AT Core Patient Profile

HL7ATCorePatientExample03-deceasedBoolean

Example with deceasedBoolean for the usage of the HL7 AT Core Patient Profile

HL7ATCorePatientExample04-Full

Example with all elements for the usage of the HL7 AT Core Patient Profile

HL7ATCorePatientExample05-FullElga

Example with all ELGA header elements in the HL7 AT Core Patient Profile

Organization-example-f001-burgers

Real-world organization example (Burgers MC) from the HL7® FHIR® specification. Note that this resource uses nothing from this implementation guide. It just exists to be referenced in the patient example resources.