This page is part of the Pharmacist Care Plan FHIR IG (v1.0.0: STU 1) based on FHIR R4. This is the current published version. For a full list of available versions, see the Directory of published versions
Contents:
This page provides a list of the FHIR artifacts defined as part of this implementation guide.
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.
Pharmacist Care Plan Server |
This section describes the expected capabilities of the Pharmacist Care Plan Consumer (aka server) actor which is responsible for creating and initiating the queries for clinical documents compliant with this specification. This CapabilityStatement imports and extends CCDAonFHIR-server CapabilityStatementCCDAonFHIR server CapabilityStatement, which imports and extends the us-core-server CapabilityStatement |
Pharmacist Care Plan Client |
This section describes the expected capabilities of the Pharmacist Care Plan Consumer (aka client) actor which is responsible for creating and initiating the queries for clinical documents compliant with this specification. This CapabilityStatement imports and extends CCDAonFHIR-client CapabilityStatementCCDAonFHIR client CapabilityStatement, which imports and extends the us-core-client CapabilityStatement |
These define constraints on FHIR resources for systems conforming to this implementation guide
PhCP-CareCoordination |
PhCP-CareCoordination |
PhCP-Coverage |
PhCP-Coverage |
PhCP-MedicationDispense |
PhCP-MedicationDispense |
PhCP-Composition |
PhCP-Composition |
PhCP-ServiceRequest |
PhCP-ServiceRequest |
PhCP-Instruction-Procedure |
PhCP-Instruction-Procedure |
PhCP-Encounter |
PhCP-Encounter |
PhCP-Organization |
PhCP-Organization |
PhCP-Intervention-Procedure |
PhCP-Intervention-Procedure |
PhCP-Medication-Therapy-Condition |
PhCP-Medication-Therapy-Condition |
These are example instances that show what data produced and consumed by systems conforming with this implementation guide might look like
PhCP-Composition-Example |
PhCP-Composition-Example |
phcp-patient-example |
phcp-patient-example |
phcp-practitioner-example |
phcp-practitioner-example |
phcp-practitionerrole-example |
phcp-practitionerrole-example |
phcp-organization-example |
phcp-organization-example |
phcp-relatedperson-example |
phcp-relatedperson-example |
phcp-communication-example |
phcp-communication-example |
phcp-payer-organization-example |
phcp-payer-organization-example |
phcp-coverage-example |
phcp-coverage-example |
phcp-encounter-example |
phcp-encounter-example |
phcp-procedure-example |
phcp-procedure-example |
phcp-intervention-procedure-example |
phcp-intervention-procedure-example |
phcp-medication-therapy-condition-example |
phcp-medication-therapy-condition-example |
phcp-medicationdispense-example |
phcp-medicationdispense-example |
phcp-servicerequest-example |
phcp-servicerequest-example |
phcp-bundle-example |
Pharmacist Care Plan Document Example |
These are resources that are used within this implementation guide that do not fit into one of the other categories
terminology-settings |
Parameters resource to specify the US version of SNOMED. |