This publication includes IP covered under the following statements.
This material contains content that is copyright of SNOMED International. Implementers of these specifications must have the appropriate SNOMED CT Affiliate license - for more information contact https://www.snomed.org/get-snomed
or info@snomed.org
.
Note: this search searches the current build of HL7® Austria FHIR® Core Implementation Guide. This page only exists for the CI build - published versions will use a different search page.
( src
)
CodeSystem for Austrian Funktionscodes Excerpt - HL7® Austria FHIR® Core Implementation Guide v2.1.0 ( src
)
CodeSystem for Austrian Funktionscodes Excerpt - JSON Representation - HL7® Austria FHIR® Core Implementation Guide v2.1.0 ( src
)
CodeSystem for Austrian Funktionscodes Excerpt - TTL Representation - HL7® Austria FHIR® Core Implementation Guide v2.1.0 ( src
)
CodeSystem for Austrian Funktionscodes Excerpt - XML Representation - HL7® Austria FHIR® Core Implementation Guide v2.1.0 ( src
)
Complex Extension: DEPRECATED 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](https://termpub.gesundheit.gv.at:443/TermBrowser/gui/main/main.zul?loadType=CodeSystem&loadName=HL7 AT ReligionAustria) for religion and is therefore aligned with the ELGA ValueSet, respectively. ( src
)
Composition Terminology Date - HL7® Austria FHIR® Core Implementation Guide v2.1.0 ( src
)
Composition Terminology Date - JSON Representation - HL7® Austria FHIR® Core Implementation Guide v2.1.0 ( src
)
Composition Terminology Date - TTL Representation - HL7® Austria FHIR® Core Implementation Guide v2.1.0 ( src
)
Composition Terminology Date - XML Representation - HL7® Austria FHIR® Core Implementation Guide v2.1.0 ( src
)
Currently, the Austrian EHR system (ELGA) is mainly based on HL7® CDA®. In order to enable the creation of FHIR® resources that have a similar data structure this Implementation Guide provides mappings to the CDA® based implementation guides (e.g. Mappings for Allgemeiner Implementierungsleitfaden v3).
Furthermore ELGA is using the HL7® Austria FHIR® Core IG as a basis for their FHIR® Implementation Guides. ( src
)
DEPRECATED 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. ( src
)
DEPRECATED 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](https://termpub.gesundheit.gv.at:443/TermBrowser/gui/main/main.zul?loadType=CodeSystem&loadName=HL7 AT ReligionAustria) for religion and is therefore aligned with the ELGA ValueSet, respectively. ( src
)
Data Type Profile:
HL7® AT Core Address Profile
( src
)
Data Type Profile:
HL7® AT Core ExtendedContactDetail Profile
( src
)
Data Type Profile: HL7® AT Core Address Profile -
JSON Profile
( src
)
Data Type Profile: HL7® AT Core Address Profile -
TTL Profile
( src
)
Data Type Profile: HL7® AT Core Address Profile -
XML Profile
( src
)
Data Type Profile: HL7® AT Core Address Profile - Change History ( src
)
Data Type Profile: HL7® AT Core Address Profile - Detailed Descriptions ( src
)
Data Type Profile: HL7® AT Core Address Profile - Examples ( src
)
Data Type Profile: HL7® AT Core Address Profile - Mappings ( src
)
Data Type Profile: HL7® AT Core Address Profile - Testing ( src
)
Data Type Profile: HL7® AT Core ExtendedContactDetail Profile -
JSON Profile
( src
)
Data Type Profile: HL7® AT Core ExtendedContactDetail Profile -
TTL Profile
( src
)
Data Type Profile: HL7® AT Core ExtendedContactDetail Profile -
XML Profile
( src
)
Data Type Profile: HL7® AT Core ExtendedContactDetail Profile - Change History ( src
)
Data Type Profile: HL7® AT Core ExtendedContactDetail Profile - Detailed Descriptions ( src
)
Data Type Profile: HL7® AT Core ExtendedContactDetail Profile - Examples ( src
)
Data Type Profile: HL7® AT Core ExtendedContactDetail Profile - Mappings ( src
)
Data Type Profile: HL7® AT Core ExtendedContactDetail Profile - Testing ( src
)
Feedback requested:
This is a first draft concerning the integration of test artifacts in an HL7® Austria FHIR® IG. The TC FHIR® likes to get feedback from implementers and balloters about the usefulness as well as the representation of testing information. Therefore, the limited scope is on purpose.
Please, also provide feedback on potential improvements for this page. ( src
)
HL7® AT Core ValueSet Profile - HL7® Austria FHIR® Core Implementation Guide v2.1.0 ( src
)
HL7® AT Core ValueSet Profile - JSON Representation - HL7® Austria FHIR® Core Implementation Guide v2.1.0 ( src
)
HL7® AT Core ValueSet Profile - TTL Representation - HL7® Austria FHIR® Core Implementation Guide v2.1.0 ( src
)
HL7® AT Core ValueSet Profile - XML Representation - HL7® Austria FHIR® Core Implementation Guide v2.1.0 ( src
)
HL7® Austria FHIR® Core Extension for documenting the date of last synchronization of the locally stored value sets for usage by the content creating system with the terminology server. ( src
)
HL7® Austria FHIR® Core Extension for the additional information part of the Austrian address. ( src
)
HL7® Austria FHIR® Core Extension for the administrative gender of a person (Patient, Practitioner, …).
The extension is used to add the missing codes and is applied in case the code for administrative gender itself is set to 'other'. ( src
)
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. ( src
)
HL7® Austria FHIR® Core Extension for the municipality code (Gemeindecode) part of the Austrian address. The municipality code is related to the municipality key (Gemeindekennziffer). While these two are generally identical, there is one notable exception: in Vienna, the municipality key (Gemeindekennziffer) is consistently 90001, whereas the municipality code (Gemeindecode) varies by district. The current list of values is provided by Statistik Austria. ( src
)
HL7® Austria FHIR® Core Extension for the municipality key (Gemeindekennziffer) part of the Austrian address. The municipality key is related to the municipality code (Gemeindecode). While these two are generally identical, there is one notable exception: in Vienna, the municipality key (Gemeindekennziffer) is consistently 90001, whereas the municipality code (Gemeindecode) varies by district. The current list of values is provided by Statistik Austria. ( src
)
HL7® Austria FHIR® Core Implementation Guide ( src
)
HL7® Austria FHIR® Core Implementation Guide ( src
)
HL7® Austria FHIR® Core Implementation Guide / ( src
)
HL7® Austria FHIR® Core Implementation Guide, published by HL7® Austria, TC FHIR®. This guide is not an authorized publication; it is the continuous build for version 2.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7Austria/HL7-AT-FHIR-Core-R5/ and changes regularly. See the Directory of published versions ( src
)
HL7® Austria FHIR® Core Profile for a related person in Austria.
The HL7® AT Core RelatedPerson is based upon the core FHIR® RelatedPeson Resource and designed to meet the applicable demographic data elements in Austria. Note, this extension represents the common structure of a person information within Austrian information systems. ( src
)
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. ( src
)
HL7® Austria FHIR® Core Profile for healthcare service data in Austria. ( src
)
HL7® Austria FHIR® Core Profile for location data in Austria. ( src
)
HL7® Austria FHIR® Core Profile for organization data in Austria. ( src
)
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. ( src
)
HL7® Austria FHIR® Core Profile for practitioner data in Austria. ( src
)
HL7® Austria FHIR® Core Profile for practitioner role data in Austria. ( src
)
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. ( src
)
HL7® Austria FHIR® Core Profile to use the profile for address data in Austria on the datatype ExtendedContactDetail. ( src
)
HL7® Austria is an official Affiliate of HL7® International. Within HL7® Austria the technical committee for FHIR® (TC FHIR®) is responsible to promote and disseminate the new upcoming standard HL7® FHIR®.
The TC FHIR® deals with the standard-compliant and coordinated usage of HL7® FHIR® based communication solutions.
It coordinates and describes necessary localizations and offers concrete help for FHIR®-compliant interfaces. ( src
)
HL7® International extension for Patient Religion ( src
)
HL7®, HEALTH LEVEL SEVEN® and FHIR® are trademarks owned by Health Level Seven International, registered with the United States Patent and Trademark Office. ( src
)
On this site you will find an overview of the FHIR® TestScripts defined within the HL7® Austria FHIR® Core Implementation Guide. The tests covered by this IG serve as a comprehensive framework to validate the functionality, interoperability, and compliance of the implemented FHIR® specifications. This document outlines the systematic approach to testing various components within the FHIR® Implementation Guide, ensuring that healthcare systems effectively exchange and utilize health data in a standardized and interoperable manner. Through a structured testing process, this test plan aims to identify and address potential issues, guaranteeing the seamless integration of FHIR® standards and the successful deployment of healthcare solutions. ( src
)
Simple Extension with the type Coding: HL7® Austria FHIR® Core Extension for the administrative gender of a person (Patient, Practitioner, ...).
The extension is used to add the missing codes and is applied in case the code for administrative gender itself is set to 'other'. ( src
)
Simple Extension with the type date: HL7® Austria FHIR® Core Extension for documenting the date of last synchronization of the locally stored value sets for usage by the content creating system with the terminology server. ( src
)
Simple Extension with the type 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. ( src
)
Simple Extension with the type string: HL7® Austria FHIR® Core Extension for the additional information part of the Austrian address. ( src
)
Simple Extension with the type string: HL7® Austria FHIR® Core Extension for the municipality code (Gemeindecode) part of the Austrian address. The municipality code is related to the municipality key (Gemeindekennziffer). While these two are generally identical, there is one notable exception: in Vienna, the municipality key (Gemeindekennziffer) is consistently 90001, whereas the municipality code (Gemeindecode) varies by district. The current list of values is provided by Statistik Austria. ( src
)
Simple Extension with the type string: HL7® Austria FHIR® Core Extension for the municipality key (Gemeindekennziffer) part of the Austrian address. The municipality key is related to the municipality code (Gemeindecode). While these two are generally identical, there is one notable exception: in Vienna, the municipality key (Gemeindekennziffer) is consistently 90001, whereas the municipality code (Gemeindecode) varies by district. The current list of values is provided by Statistik Austria. ( src
)
System OID - HL7® Austria FHIR® Core Implementation Guide v2.1.0 ( src
)
System OID - JSON Representation - HL7® Austria FHIR® Core Implementation Guide v2.1.0 ( src
)
System OID - TTL Representation - HL7® Austria FHIR® Core Implementation Guide v2.1.0 ( src
)
System OID - XML Representation - HL7® Austria FHIR® Core Implementation Guide v2.1.0 ( src
)
Table of Contents - HL7® Austria FHIR® Core Implementation Guide v2.1.0 ( src
)
The (c) symbol should NOT be included in this string. It will be added by software when rendering the notation. Full details about licensing, restrictions, warrantees, etc. goes in the more general 'copyright' element. ( src
)
The HL7® Austria FHIR® Core Implementation Guide (IG) covers administrative Resources, like Patient, Organization, Practitioner, etc. that can be used on their own with no specific functional requirements for usage or they can be used for other more functional FHIR® IGs in Austria via dependencies. It contains only those Profiles and Extension where adaptions for Austria were necessary. ( src
)
This guide defines the minimum constraints on the FHIR® resources to create the Austrian Core Profiles. ( src
)
This guide is a working specification. We anticipate that it will be implemented and tested by FHIR® system producers whose feedback will help improve its content. With this standard for trial use, we are looking for feedback on whether the following goals have been met: ( src
)
This implementation guide is provided to support the use of FHIR® in Austria. ( src
)
This is the implementation guide for the Core Profiles (v2.1.0: STU 3) based on HL7® FHIR® R5. It is a ballot implementation guide that is hosted on the HL7® Austria github project. The most recent version of this implementation guide can be found at the HL7® Austria FHIR® Website. ( src
)
HL7® Austria FHIR® Core Implementation Guide, published by HL7® Austria, TC FHIR®. This guide is not an authorized publication; it is the continuous build for version 2.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/HL7Austria/HL7-AT-FHIR-Core-R5/
and changes regularly. See the Directory of published versions
HL7® Austria FHIR® Core Extension for the municipality code (Gemeindecode) part of the Austrian address. The municipality code is related to the municipality key (Gemeindekennziffer)
. While these two are generally identical, there is one notable exception: in Vienna, the municipality key (Gemeindekennziffer) is consistently 90001, whereas the municipality code (Gemeindecode) varies by district. The current list of values is provided by Statistik Austria
.
Simple Extension with the type string: HL7® Austria FHIR® Core Extension for the municipality code (Gemeindecode) part of the Austrian address. The municipality code is related to the municipality key (Gemeindekennziffer)
. While these two are generally identical, there is one notable exception: in Vienna, the municipality key (Gemeindekennziffer) is consistently 90001, whereas the municipality code (Gemeindecode) varies by district. The current list of values is provided by Statistik Austria
.
HL7® Austria FHIR® Core Extension for the municipality key (Gemeindekennziffer) part of the Austrian address. The municipality key is related to the municipality code (Gemeindecode)
. While these two are generally identical, there is one notable exception: in Vienna, the municipality key (Gemeindekennziffer) is consistently 90001, whereas the municipality code (Gemeindecode) varies by district. The current list of values is provided by Statistik Austria
.
Simple Extension with the type string: HL7® Austria FHIR® Core Extension for the municipality key (Gemeindekennziffer) part of the Austrian address. The municipality key is related to the municipality code (Gemeindecode)
. While these two are generally identical, there is one notable exception: in Vienna, the municipality key (Gemeindekennziffer) is consistently 90001, whereas the municipality code (Gemeindecode) varies by district. The current list of values is provided by Statistik Austria
.
DEPRECATED
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.
The identifiers are distinguished by the identifier type code of the HL7 v2 table 0203: “SS” (Social Security number) for the SVNR, “NI” (National unique individual identifier) for the bPK, “ANON” (Anonymous identifier) for the vbPK and “PI” (Patient internal identifier) for the local patient identifier. Further identifier types can be found in the HL7 AT Patient Identifier
value set.
This value set was designed for the HL7AT Core IGs (R4 and R5) and will be moved to the Austrian e-Health terminology server
, depending on the outcome of the ballot.
This is the implementation guide for the
Core Profiles (v2.1.0: STU 3)
based on HL7® FHIR® R5. It is a ballot
implementation guide that is hosted on the HL7® Austria github project
. The most recent version of this implementation guide can be found at the HL7® Austria FHIR® Website
.
This is the implementation guide for the
Core Profiles (v2.1.0: STU 3)
based on HL7® FHIR® R5. It is a ballot
implementation guide that is hosted on the HL7® Austria github project
. The most recent version of this implementation guide can be found at the HL7® Austria FHIR® Website
.
This guide contains no code systems or value sets on its own. Note, that code systems and value sets that are used in the various Profiles or Extensions of this guide will generally be made available via a separate IG on the Austrian Terminology Server
based on TerminoloGit
.
It does contain an Extension and a Profile for the ValueSet Resource, that allows to add the OID of code systems that are referenced within the ValueSet, not just the URL reference.
This profile is already used by the Austrian Terminology Server.
This guide contains no code systems or value sets on its own. Note, that code systems and value sets that are used in the various Profiles or Extensions of this guide will generally be made available via a separate IG on the Austrian Terminology Server
based on TerminoloGit
.
It does contain an Extension and a Profile for the ValueSet Resource, that allows to add the OID of code systems that are referenced within the ValueSet, not just the URL reference.
This profile is already used by the Austrian Terminology Server.
The TestScript resources presented here were created in cooperation with AEGIS.net Inc.
and can readily be used in Touchstone
for testing the resources defined within this Implementation Guide.
The TestScript resources presented here were created in cooperation with AEGIS.net Inc.
and can readily be used in Touchstone
for testing the resources defined within this Implementation Guide.
