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

Behavior: Capability Statements

The following artifacts define the specific capabilities that different types of systems are expected to have in order to comply with this implementation guide. Systems conforming to this implementation guide are expected to declare conformance to one or more of the following capability statements.

Adapter capabilities

Behavior: Search Parameters

These define the properties by which a RESTful server can be searched. They can also be used for sorting and including related resources.

composition	The first resource in the bundle, if the bundle type is “document” - this is a composition, and this parameter provides access to search its contents
type	document message transaction transaction-response batch batch-response history searchset collection
subject	Who and/or what the composition is about
identifier	A patient identifier
type	Multiple Resources: ​AllergyIntolerance: allergy intolerance - Underlying mechanism (if known) ​Composition: Kind of composition (LOINC if possible) ​DocumentManifest: Kind of document set ​DocumentReference: Kind of document (LOINC if possible) ​Encounter: Specific type of encounter ​EpisodeOfCare: Type/class - e.g. specialist referral, disease management

Structures: Resource Profiles

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

AdapterDefinition

Example: Example Instances

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

Adapter