This page is part of the Post Acute Orders FHIR IG (v0.2.0: STU 1 Ballot 2) based on FHIR R4. . For a full list of available versions, see the Directory of published versions

FHIR Artifacts Overview

Previous Page - Technical Background

Artifact Lists

Complying with this implementation guide means complying with a number of profiles, extensions, code systems, value sets and custom search parameters. This page provides an overview of where the relevant information can be found.

The FHIR artifacts used by Post-acute Orders are organized, in this section, based on the origin of the content (e.g. part of the US Core implementation guide or specific to this implementation guide).

Post-acute Order specific Artifacts that do not have US Core R4 profiles

• Bundle
• MessageHeader
• Task
• Subscription
• DeviceRequest
• ServiceRequest
• Coverage

Post-Acure Order specific Artifacts based on US Core R4 profiles

• MedicationRequest
• Medication
• Provenance

US Core R4 profiles referenced by the above resources

• Patient
• Practitioner
• PractitionerRole
• Organization
• Location

Additional information about the use of these artifacts can be found in the relevant specification.

The artifacts are of four types:

• Profiles that constrain FHIR resources to reflect PAO requirements.
• Extensions that define additional data elements that can be conveyed as part of a resource.
• Code Systems that define PAO-specific terminologies to be used in one or more of the profiles.
• Value Sets that define the specific subsets of both PAO-defined and other code systems that can be (or are recommended to be) used within one or more profile elements.
• Operations that define the PAO-specific constraints on the $processMessage operation

Next Page - Must Support and Missing Data