Pharmacist Services and Summaries - FHIR (PhCP)
1.0.0 - STU Release 1.0.0 for FHIR R4

Publication Build: This will be filled in by the publication tooling

## Specification

Previous Page - Background

### FHIR Documents

The Pharmacist Care Plan document relies on the FHIR Documents paradigm. Implementers need to be aware of and follow all the rules required for FHIR Documents. Please refer to that section of the core FHIR spec.

http://hl7.org/fhir/documents.html

### Actors

This specification defines no new actors beyond those in the C-CDA on FHIR specification.

### Profiles and Extensions

To claim conformance to a Pharmacist e-Care Plan Profile, servers SHALL:

- Be able to populate all profile data elements that have a minimum cardinality >= 1 and/or flagged as Must Support as defined by that profile’s StructureDefinition.
- Conform to this IG’s Server Capability Statement expectations for that profile’s type.

The following profiles and extensions are present in the specification. Details on these profiles and extensions are available on the Artifact Index page.

#### Resource Profiles

- PhCP-CareCoordination
- PhCP-Coverage
- PhCP-MedicationDispense
- PhCP-Composition
- PhCP-ServiceRequest
- PhCP-Instruction-Procedure
- PhCP-Encounter
- PhCP-Organization
- PhCP-Intervention-Procedure
- PhCP-Medication-Therapy-Condition

#### Extensions

This implementation guide defines no new extensions beyond those defined in C-CDA on FHIR.

### Document Bundles

Per the FHIR Document’s paradigm, the Composition resource and all references resources must be packaged in a FHIR Bundle resource where Bundle.type = document in order for the content in the Composition resource to be considered a “document”. Un-bundled Composition resources are useful while a document is being edited, but until it has been bundled it does not meet the key characteristics of a clinical document (persistence, potential for authentication, etc.). The FHIR specification includes a $document operation on the Composition resource, and FHIR servers that support that operation can handle the task of bundling Composition and other resources.

See the documentation on the FHIR Bundle resource and the FHIR $document operation for more information.

### US Core and C-CDA on FHIR

The Pharmacist Care Plan specification depends on the C-CDA on FHIR and US Core specifications.

More information on C-CDA on FHIR can be found here. More information on US Core can be found here.

### Must Support

This specification uses the same must-support rules as the C-CDA on FHIR specification.

Next Page - Acknowledgments