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 in it's permanent home (it will always be available at this URL). For a full list of available versions, see the Directory of published versions

Background

Previous Page - Home Page

Purpose

This document describes constraints on the C-CDA on FHIR header and body elements for the Pharmacist Care Plan, which are derived from requirements set forth by the Pharmacy Health Information Technology (HIT) Collaborative and the National Council for Prescription Drug Programs (NCPDP) WG10 Professional Pharmacy Services, vendors, and Health Level Seven (HL7) stakeholder workgroups. Templates in this US Realm implementation guide are specific to pharmacy management treatment and interventions that will promote interoperability and will create information suitable for reuse in quality measurement, public health reporting, research, and reimbursement.

This guide contains a library of FHIR profiles and is compliant with FHIR Release 4.

Audience

The audience for this document includes pharmacy vendors, software developers, and implementers with reporting capabilities within their electronic health record (EHR) systems; developers and analysts in receiving institutions; and local, regional, and national health information exchange networks who wish to create or process pharmacy clinical documents according to this specification.

Business analysts and policy managers can also benefit from a basic understanding of the use of FHIR profiles across multiple implementation use cases.

General Background

Pharmacists work in multiple environments (community, hospital, long term care, clinics, etc.) and increasingly participate in patient-centered care teams providing essential clinically-oriented patient care services such as medication therapy management, clinical reconciliation (medication, allergies and problems), patient immunization management, disease state monitoring, and therapy adherence programs. These services reduce adverse drug events, improve patient safety, and optimize medication use and health outcomes. Pharmacists are integral members of the health care team and have unique and frequent access to patients, routinely working with patients to facilitate understanding and compliance with drug regimens, reconcile medications from multiple prescribers, and monitor effectiveness of the treatment. These activities affect the treatment plans of other caregivers. Having a medication-related plan of care shared with those providers and incorporated with care plans developed by other care team members is critical to the overall success of patients reaching their proposed care goals of care.

Today, pharmacists document within proprietary systems that do not export and cannot receive standards-based data. Where care plan information is shared from pharmacy management systems, it is done using proprietary interfaces and free text; there is no standard covering pharmacist care plans. Thus, sharing data requires time consuming redundant data entry which is a major factor limiting care planning. Furthermore, care plan documentation that is free text is inconsistent and incapable of supporting electronic quality measurement and reporting.

Current Project

The current project specifies the Pharmacist Care Plan, an electronic care plan document with enhanced medication management content based on the profiles in the C-CDA on FHIR specification. The Pharmacist Care Plan is a standardized, interoperable document containing information on medication-related activities, as well as patient-provider shared goals and plans for care. The Pharmacist Care Plan identifies resources for and obstacles to patient compliance with the recommended treatment. This type of data is not often captured in a structured and standard format that can be used for research, quality measurement, or public health reporting. The Pharmacist Care Plan supports the strategy of interoperability and information exchange promoting coordination of care among a variety of settings, thus improving the quality of care for the patient.

The Pharmacist Care Plan serves two needs. It supports the CMS Medicare Part D Enhanced Medicare Therapy Management (MTM) program that started on January 1, 2017. The program launched a pilot in five Medicare Part D regions. Program participants in these regions have the opportunity coordinate care with pharmacy providers on issues related to medication management and adverse outcomes through the MTM model of enhanced care, which includes an individuals goals for therapy and outcomes.

Secondly, the movement towards value-based payment (VBP) models has recognized pharmacists as an important part of the well-connected care team that addresses the needs of the patient. In a VBP model, a patients care is coordinated, managed, and supported through documentation of goals and outcomes. The Pharmacist Care Plan provides that documentation for medications and medication-related issues.

The current project builds on the work started in the NCPDP Pharmacist eCare Plan, which provides guidance for pharmacist and vendors as they implement the standard CDA R2.1 Care Plan document. The Pharmacist Care Plan electronic document standardizes exchange of information on medications dispensed and medication therapy problems which are not specified in the current Care Plan document type. This version contains reconciled ballot comment changes and includes pharmacy HIT value sets that are published in the Value Set Authority Center (VSAC).

The project has implemented both the CDA and the FHIR (Fast Healthcare Interoperability Resources) Pharmacist Care Plan specifications in a pilot at Community Care of North Carolina (CCNC) and ongoing use at Community Pharmacy Enhanced Service Network (CPESN) USA.. Please note, this FHIR Pharmacist Care Plan is balloted separately from the CDA standard. The burden of redundant data entry is a major factor limiting care planning to less than 15% of the CCNC population, which includes many at risk and care-intensive patients. Reducing redundant data entry and providing standard, structured data will enhance the ability of pharmacists to engage with patients and will improve the patient experience of care through comprehensive medication review with the pharmacists and care managers. Facilities received Pharmacist Care Plan files in both CDA and FHIR formats from implementing EHRs. In addition, participating systems convert CDA-based Pharmacist Care Plans to the FHIR format using transformation files.

Use Cases

This implementation guide meets the need of four use cases unique to the pharmacy environment. Though the scope of the pilot testing focused on Use Case 4, the standard was designed to meet the needs for clinical data exchange in each of the cases described in this section.

Use Case 1: New condition for a patient at risk for a pulmonary embolism

The community pharmacist meets with the patient and the caregiver after a recent discharge from a hospital for a pulmonary embolism. The patient is diagnosed with hypertension and diabetes. The patient has been enrolled in a diabetes outpatient clinic and has now been referred to an anticoagulation outpatient clinic. The community pharmacist coordinates medication therapy management services (including reconciliation of medications, allergies and indications for medication use) with the primary care provider (PCP) and the diabetes and anticoagulation clinics and documents the patients medication-related goals. The pharmacy generates the Pharmacist Care Plan to share medication related goals and electronically delivers the Care Plan to the patient, the PCP, and the outpatient clinics for chronic care management and care coordination.

Use Case 2: Patient scheduled for a hip replacement

The pharmacist, under a collaborative practice agreement with the orthopedic surgeon, counsels the patient prior to the procedure to ensure there are no medication-related problems. After the surgery, the pharmacist coordinates medication-related goals with the patient pertaining to deep vein thrombosis risk and pain management.

The community pharmacist uses a health IT system to document patient care. The health IT system generates the Pharmacist Care Plan to share the medication related goals electronically with the patient, orthopedic surgeon, PCP, home health care agency, and the rehabilitation center for care coordination.

Use Case 3: Patient with behavioral health issues and multiple chronic diseases meets with a consultant pharmacist for the yearly comprehensive medication review to meet Medicare Part D MTM requirement

The pharmacist documents conflicting treatment strategies and medications. The pharmacist recommends strategies/alterations to existing treatment, development of a manageable medication schedule, patient education, and outcome follow-up.

The community pharmacist uses a health IT system to document patient care. The health IT system generates the Pharmacist Care Plan to share the medication related goals and strategies electronically with the patient, the psychiatrist, the outpatient psychiatric clinic, and the PCP or chronic care management and care coordination.

Use Case 4: Patient comes to the community pharmacy to pick up hydrocodone, which has been e-prescribed and complaints of constipation

The pharmacist reviews the state Prescription Drug Monitoring Program (PDMP) database and discovers that multiple physicians have treated the patient for pain. The pharmacist suspects the patient may have an opioid abuse condition. Through patient assessment using a validated nutrition screening tool, the pharmacist discovers the patient shows signs of potential malnutrition, has three chronic care conditions, complains of constipation, and has no PCP. The pharmacist performs comprehensive medication review and helps the patient identify a PCP.

The community pharmacist documents conflicting treatment strategies and medications including the need for naloxone. The pharmacist recommends strategies/alterations to existing treatment, pain management, development of a manageable medication schedule, nutritional counseling, patient education, and outcome follow-up.

Mappings

The following table contains mappings between the CDA and FHIR versions of the Pharmacist Care Plan document type.

Data Element	FHIR Contained by	FHIR Resource	FHIR Element Path	CDA Section	CDA Mapping
Date of the Report		Composition [PhCP-Composition]	date	US Realm Header (V3)	ClinicalDocument/effectiveTime
ID of the PhCP Document		Composition [PhCP-Composition]	id	US Realm Header (V3)	ClinicalDocument/id
Provider ID	PhCP-Encounter.particpant	Practitioner	identifier	Pharmacist Care Plan Document	ClinicalDocument/componentOf/encompassingEncounter/responsibleParty/assignedEntity/id
Provider Name	PhCP-Encounter.participant	Practitioner	name	Pharmacist Care Plan Document	ClinicalDocument/componentOf/encompassingEncounter/responsibleParty/assignedEntity/assignedPerson/name
Provider Phone	PhCP-Encounter.participant	Practitioner	telecom[system="phone"]	Pharmacist Care Plan Document	ClinicalDocument/componentOf/encompassingEncounter/responsibleParty/assignedEntity/telecom
Provider Fax	PhCP-Encounter.participant	Practitioner	telecom[system="fax"]	Pharmacist Care Plan Document	ClinicalDocument/componentOf/encompassingEncounter/responsibleParty/assignedEntity/telecom
Provider Email	PhCP-Encounter.participant	Practitioner	telecom[system="email"]	Pharmacist Care Plan Document	ClinicalDocument/componentOf/encompassingEncounter/responsibleParty/assignedEntity/telecom
Provider Facility/Office Name	PhCP-Encounter.location	Location	name	Pharmacist Care Plan Document	ClinicalDocument/componentOf/encompassingEncounter/location
Provider Address	PhCP-Encounter.participant	Practitioner	address	Pharmacist Care Plan Document	ClinicalDocument/componentOf/encompassingEncounter/responsibleParty/assignedEntity/addr
Facility ID Number	PhCP-Encounter.location	Location	identifier	Pharmacist Care Plan Document	ClinicalDocument/componentOf/encompassingEncounter/location/healthCareFacility/id
Facility Name	PhCP-Encounter.location	Location	name	Pharmacist Care Plan Document	ClinicalDocument/componentOf/encompassingEncounter/location/healthCareFacility/serviceProviderOrganization/name
Facility Type	PhCP-Encounter.location	Location	type	Pharmacist Care Plan Document	ClinicalDocument/componentOf/encompassingEncounter/location/healthCareFacility/serviceProviderOrganization/code
Facility Phone	PhCP-Encounter.location	Location	telecom[system="phone"]	Pharmacist Care Plan Document	ClinicalDocument/componentOf/encompassingEncounter/location/healthCareFacility/serviceProviderOrganization/telecom[@use="phone"]
Facility FAX	PhCP-Encounter.location	Location	telecom[system="fax"]	Pharmacist Care Plan Document	ClinicalDocument/componentOf/encompassingEncounter/location/healthCareFacility/serviceProviderOrganization/telecom
Facility Address	PhCP-Encounter.location	Location	address	Pharmacist Care Plan Document	ClinicalDocument/componentOf/encompassingEncounter/location/healthCareFacility/location/addr
Patient ID Number	Composition.subject	Patient	identifier	US Realm Header (V3)	ClinicalDocument/recordTarget/patientRole/id
Patient Name	Composition.subject	Patient	name	US Realm Header (V3)	ClinicalDocument/recordTarget/patientRole/patient/name
Patient Phone	Composition.subject	Patient	telecom[system="phone"]	US Realm Header (V3)	ClinicalDocument/recordTarget/patientRole/telecom
Patient Email	Composition.subject	Patient	telecom[system="email"]	US Realm Header (V3)	ClinicalDocument/recordTarget/patientRole/telecom
Parent/ Guardian Name	Composition.subject	Patient	contact	US Realm Header (V3)	ClinicalDocument/recordTarget/patientRole/patient/guardian/guardianPerson/name
Parent/ Guardian Phone	Composition.subject	Patient	contact.telecom[system="phone"]	US Realm Header (V3)	ClinicalDocument/recordTarget/patientRole/patient/guardian/telecom
Parent/ Guardian Email	Composition.subject	Patient	contact.telecom[system="email"]	US Realm Header (V3)	ClinicalDocument/recordTarget/patientRole/patient/guardian/telecom
Patient Street Address	Composition.subject	Patient	address	US Realm Header (V3)	ClinicalDocument/recordTarget/patientRole/addr
Patient Birth Date	Composition.subject	Patient	birthDate	US Realm Header (V3)	ClinicalDocument/recordTarget/patientRole/patient/birthTime
Patient Sex	Composition.subject	Patient	gender	US Realm Header (V3)	ClinicalDocument/recordTarget/patientRole/patient/administrativeGenderCode
Patient Race	Composition.subject	Patient	extension	US Realm Header (V3)	ClinicalDocument/recordTarget/patientRole/patient/raceCode
Patient Ethnicity	Composition.subject	Patient	extension	US Realm Header (V3)	ClinicalDocument/recordTarget/patientRole/patient/ethnicGroupCode
Preferred Language	Composition.subject	Patient	communication.language	US Realm Header (V3)	ClinicalDocument/recordTarget/patientRole/patient/languageCommunication
Occupation	Composition.section	Observation	value	Social History Section (V3)	Social History Observation (V3)/code
Pregnant	Composition.section	Observation	value	Social History Section (V3)	Pregnancy Observation/code
Hospital Unit	PhCP-Encounter.location	Location	type	Pharmacist Care Plan Document	ClinicalDocument/componentOf/encompassingEncounter/location/healthCareFacility/code
Visit Date/Time	PhCP-Encounter.location	Location	period.start	Pharmacist Care Plan Document	ClinicalDocument/componentOf/encompassingEncounter/effectiveTime/low
Admission Date/Time	PhCP-Encounter.location	Location	period.start	Pharmacist Care Plan Document	ClinicalDocument/componentOf/encompassingEncounter/effectiveTime/low
Discharge Date/Time	PhCP-Encounter.location	Location	period.end	Pharmacist Care Plan Document	ClinicalDocument/componentOf/encompassingEncounter/effectiveTime/high
History of Present Illness		Composition.section	text	History of Present Illness Section	text
Reason for Visit		Composition.section	text	Reason for Visit Section	text
Date of Onset	Composition.section	Condition	onset	Problem Section (entries required) (V3)	Problem Concern Act (V3)/Problem Observation (V3)/effectiveTime + Problem Concern Act (V3)/Initial Case Report Trigger Code Problem Observation/effectiveTime
Symptoms (list)	Compostion.section	Observation	code	Problem Section (entries required) (V3)	Problem Concern Act (V3)/Problem Observation (V3)/value
Lab Order Code	Composition.section	ServiceRequest	code	Plan of Treatment Section (V2)	Planned Observation (V2)/code
Lab Order Code (Trigger)	Composition.section	ServiceRequest		Plan of Treatment
Laboratory Results	Composition.section	Observation	code OR value	Results Section (V3)	Result Observation (V3)/code OR Result Observation (V3)/value
Laboratory Result (Trigger)	Composition.section	Observation		Results Section (V3)
Filler Order Number	Composition.section	Observation	identifier	Results Section (V3)	Result Organizer (V3)/id
Diagnoses	Composition.section	Observation	code	Problem Section (entries required) (V3)	Problem Observation (V3)/code
Diagnosis (Trigger)	Composition.section	Observation		Problem Section (entries required) (V3)
Date of Diagnosis	Composition.section	Observation	effective[x]	Problem Section (entries required) (V3)	Problem Observation (V3)/effectiveTime
Medications Administered (list)	Composition.section	MedicationStatement	medication[x]	Medications Administered Section (V2)	Medication Information (V2)/manufacturedMaterial/code
Death Date	Composition.subject	Patient	deceased[x]	Pharamacist Care Plan Document	ClinicalDocument/recordTarget/patientRole/patient/sdtc:deceasedInd
Immunization Status	Composition.section	Immunization	status	Immunizations Section (entries required) (V3)	Immunization Activity (V3)/statusCode
Travel History Dates	Composition.section	Observation	effective[x]	Social History Section (V3)
Travel History Location - Free Text	Composition.section	Observation	valueCodeableConcept.text	Social History Section (V3)
Travel History Location - Coded	Composition.section	Observation	valueCodeableConcept.coding	Social History Section (V3)
Travel History Location - Address	Composition.section	Observation		Social History Section (V3)

Next Page - Specification