HL7® Austria TC FHIR® Messaging
0.1.0 - ci-build

Artifacts Summary

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

Behavior: Message Definitions

These define the types of messages that can be sent and/or received by systems conforming to this implementation guide.

Communication over directed messaging.

Regulates the resources to be used in a directed message when transferring a Communication.

Communication request over directed messaging.

Regulates the resources to be used in a directed message when performing a CommunicationRequest.

Document transfer over directed messaging.

Regulates the resources to be used in a directed message when transferring a document.

Service request over directed messaging.

Regulates the resources to be used in a directed message when performing a ServiceRequest.

Service status update over directed messaging.

Regulates the resources to be used in a directed message when transferring a task status update of a ServiceRequest.

Structures: Resource Profiles

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

AT Messaging Communication

Communication to be used for all communication messages transfered with the AT FHIR messaging.

AT Messaging CommunicationRequest

CommunicationRequest to be used for all communication request messages transfered with the AT FHIR messaging.

AT Messaging Endpoint

Endpoint for use in the Messaging systems for AT FHIR messaging.

AT Messaging Message Bundle

MessageBundle to be used for all messages transfered with the AT FHIR messaging.

AT Messaging Message Header

MessageHeader to be used for all messages transfered with the AT FHIR messaging.

AT Messaging Task

Task to be used for all service status messages transfered with the AT FHIR messaging.

Structures: Data Type Profiles

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

AT Messaging Communication Attachment

Simple Attachment with base64 encoded content for communication over directed messaging.

Terminology: Value Sets

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

AT Message Event Type ValueSet

Extensible ValueSet consisting of the Message Event Type Codings.

AT Messaging Endpoint Type ValueSet

ValueSet of Endpoint Type Codings.

Terminology: Code Systems

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

AT Messaging Endpoint Type

Endpoint Type Coding to encode Messaging Systems the message is transported over.

AT Messaging Event Type

Event Coding for discriminating messages on the receiver.

Example: Example Instances

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

Ad-hoc message of Doctors note

Doctors note as ad-hoc submitted message (without previous request).

Communication Example

Plain text message that kindly rejects a previous communication request.

CommunicationRequest for a consultation document

Plain Text communication request for a consult document.

Consult communication

Consultation document rejection as CommunicationRequest message.

Consult request

Consult request as CommunicationRequest message.

Lab ServiceRequest

Service Request for a Blood Test.

Lab request

Lab request as ServiceRequest message.

Lab status update

Lab status update as service status update message.

MessageHeader of an ad-hoc message sending a document.

Message header for sending a doctor's note document from a HIS to a GP software without prior request.