This page provides a list of the FHIR artifacts defined as part of this implementation guide.
• You can download a list of CSVs for the profiles here.
• A zip of formatted Excel files for profiles is here.
Shared Extensions
The set of 'extra' elements that have been defined to supplement the capabilities of the base FHIR resources to meet the implementation guide requirements. These extensions are expected to have applicability across a wide variety of implementation guides.
- Coding Original Text
- Contact Point is Confidential
- Entity Service
- Message Header Application Id
- Message Header Source Conformance Version
- Issue reference number
- User-friendly issue text
- Patient PHN version
- Practitioner Authentication
- Practitioner SAML Token
- Reference Identifier
- On-Behalf-Of Organization
- Reference Practitioner Organization
Cross-project extensions
Extensions that are relevant in a specific subset of implementation guides, but which are unlikely to have general relevance. The purpose of these extensions may not be clear without first understanding the referencing implementation guide.
Data Type Profiles
Constraints and extensions on the FHIR data types used throughout the implementation guide
- Shared Health Address
- Shared Health Attachment
- Shared Health CodeableConcept
- Shared Health CodeableConcept Code
- Shared Health CodeableConcept Code Required and Text Required
- Shared Health CodeableConcept Code Required with Text Optional
- Shared Health CodeableConcept Text
- Shared Health CodeableConcept Text Required
- Shared Health CodeableConcept Text Required with Code Optional
- Shared Health ContactPoint
- Shared Health HumanName
- Shared Health Identifier
- Shared Health Person Identifier
- Shared Health Quantity
- Shared Health Money
- Shared Health Reference
Abstract Profiles
High-level, shared constraints and extensions on FHIR resources used by the implementation guide. These profiles are not used directly in the specification but serve as a foundation for other profiles that are used within the tasks and interactions.
Payload Resource Profiles
General constraints and extensions on FHIR resources used by the implementation guide. These profiles are referenced by Tasks and Interactions or by resources that are referenced by Tasks or Interactions
- Shared Health Media Fax
- Shared Health Operation Outcome
- Shared Health Organization - Base
- Shared Health Organization - eRx Service Location
- Shared Health Organization - Provider Registry
- Shared Health Patient
- Shared Health Practitioner
- Shared Health Locum Practitioner
- Shared Health Non-Clinician Practitioner
- Shared Health SAML Practitioner
- Shared Health Practitioner - Provider Registry
Interaction Profiles - Provider Registry Queries
Profiles used to define Provider Registry Query communication interactions for this implementation guide. Two types of profiles are defined. The 'Bundle' profiles define the root set of content allowed to be shared. For messaging interactions, the 'MessageHeader' profiles define the messaging events and the focal ''data'' resources for each message.
Interaction Profiles - Polling Messages
Profiles used to define Polling communication interactions for this implementation guide. Two types of profiles are defined. The 'Bundle' profiles define the root set of content allowed to be shared. For messaging interactions, the 'MessageHeader' profiles define the messaging events and the focal ''data'' resources for each message.
Interaction Profiles - Notification (Rejection Messages)
Profiles used to define Notification (Rejection Messages) communication interactions for this implementation guide. Two types of profiles are defined. The 'Bundle' profiles define the root set of content allowed to be shared. For messaging interactions, the 'MessageHeader' profiles define the messaging events and the focal ''data'' resources for each message.
- Interaction Message Header 901 - Message disposition notification
- Interaction Message Header 997 - Asynchronous message undelivered
- Interaction Message Header 998 - Asynchronous hub message rejection
- Interaction Message Header 999 - Asynchronous Message Rejection
- Interaction Bundle 901 - Message disposition notification
- Interaction Bundle 997 - Generic Recipient Asynchronous Reject
- Interaction Bundle 998 - Generic hub Asynchronous Reject
- Interaction Bundle 999 - Asynchronous message rejection
Provider Registry Search Parameters
Custom RESTful search parameters defined for use within the Shared Health ePrescription space
Conformance Statements
Descriptions of the types of systems that can participate in any of the Shared Health FHIR interfaces and what the expectations of each of those systems are.
Examples - Provider Registy Queries
Examples of the different Provider Registry Query interactions supported by this specification.