Technical Specifications
C-CDA
The pharmacist care plan can be implemented in two formats: C-CDA and FHIR. C-CDA stands for Consolidated Clinical Document Architecture and is a broadly-adopted HL7 standard for exchange of clinical data.
Read more about C-CDA here.
The C-CDA version of the pharmacist care plan is a based on the more general HL7 care plan, with changes to some section requirements and the addition of a payer section.
Hl7 CDA R2 Implementation Guide : Pharmacist Care Plan Document Introductory Materials
Hl7 CDA R2 Implementation Guide : Pharmacist Care Plan Document Templates and Supporting Information
The link below provides an example C-CDA format pharmacist care plan that includes all required sections plus additional sections showing problem observations, immunizations and vitals signs observations.
FHIR
The pharmacist care plan can be implemented in two formats: C-CDA and FHIR. FHIR stands for Fast Healthcare Interoperability Resources and is HL7’s “next generation” healthcare data standard.
Read more about FHIR here.
The FHIR version of the pharmacist care plan is based on the C-CDA on FHIR standard, so the document is profiled as a Composition resource.
The links below provide FHIR-formatted pharmacist care plans for implementers to use as examples:
Basic pharmacist care plan example in FHIR format.
Value Sets
Snomed CT codes used within the Pharmacist Care plan can be accessed from the Value Set Authority Center. Click below for more information.
How to access Value Sets from VSAC
CPESN USA provides a summary of codes that are pertinent to community pharmacy, which is updated regularly based on need.
-
Click here to download the most updated version as of 4/8/24.
There may be instances where a user may request a code that is not available. Pharmacy HIT Collaborative has created a process to request for new codes as well as a template to use for submission.
Race and Ethnicity Implementation into the eCare Plan Standard
-
Please refer to the structure definition here for the US Core patient for information about how to populate these data elements.
-
The US Core Race Extension uses OMB Race Categories to code race. Value Set: here. The categories are:
-
American Indian or Alaska Native
-
Asian
-
Black or African American
-
Native Hawaiian or Other Pacific Islander
-
White
-
-
Optionally, the “detailed” OMB Race codes can also be implemented. Value Set with 917 concepts can be accessed here.
-
OMB Categories are also used for ethnicity. Value Set: here. The two OMB ethnicity codes are:
-
Hispanic or Latino
-
Non Hispanic or Latino
-
-
As with the race codes, the detailed OMB ethnicity codes (42 concepts) can be used. Value Set here.