Skip to end of metadata
Go to start of metadata

Publication Request

Publication Request

1. Published Name of the Standard for which request is being made

2. Standards Material/Document


3. Date of Request

Feb 12, 2020

4. Use Period

2 years

5. Reason for extension, timeline, and actions

6. Original Publication Date

7. End date of the current STU period

8. Length of the requested extension

9. Review Process

10. HL7 Work Group making this request and date


10a. Requesting WG Date

11. URL of approval minutes

12. HL7 Product Management Group

FHIR Management Group

12a. Management Group Date of Approval

13. URL of approval minutes

14. Is the artifact ready for final publication?


15. If not ready, please describe remaining steps.

16. Tool name used to produce the machine processable artifacts in the IG

Trifolia on FHIR

17. The name of the “IG artifact” within the context of the above mentioned tool.


18. Balloted Name of the standard for which request is being made

HL7 FHIR® Implementation Guide: Pharmacist Care Plan Document, Release 1 - US Realm

19. Requested name for published standard

HL7 FHIR® Implementation Guide: Pharmacist Care Plan Document, Release 1 - US Realm

20. If CMET, list IDs balloted

21. Project Insight Number


22. Document Realm


23. Ballot cycle in which the document was successfully balloted


24. Results of that ballot (following reconciliation activities):

24. Results of that ballot (following reconciliation activities):

(not needed for errata, STU extension, or unballoted STU update)

25. Affirmative


26. Negative


27. Abstentions


28. Not Returned


29. Total in ballot pool


30. Date on which final document/standards material was supplied to HQ

31. URL of publication material/ SVN repository

32. Publishing Facilitator

Rick Geimer

33. Special Publication Instructions

34. URL of ballot reconciliation document

35. Has the Work Group posted its consideration of all comments received in its reconciliation document on the ballot desktop?


36. Substantive Changes Since Last Ballot?


37. Product Brief Reviewed By

38. Date Product Brief Reviewed

39. Has the Product Brief changed?

Product Brief

Product Brief

40. Family


41. Section

Implementation Guides

42. Topic

Patient Care Pharmacy

43. Please Describe the Topic

44. Product Type

Implementation Guide

45. Parent standard


46. Parent Standard Status

47. Update/replace standard

48. Common name/search keyword

Common Names/Aliases: Pharmacist Care Plan, PeCP
Search Keywords: PeCP, PhCP, ePhCP, electronic Pharmacist Care Plan

49. Description

This implementation guide specifies FHIR profiles and other artifacts 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.



These are categories of potential users, implementers, or other interested parties such as those that are indicated on the Project Scope Statement under “Stakeholders/Vendors/Providers”. Select those that are applicable, or suggest others:

50. Stakeholders

Standards Development Organizations (SDOs), Payors, Other (specify in text box below)

51. Vendors

EHR, PHR, Health Care IT, HIS, Other (please specify)

52. Providers

Healthcare Institutions (hospitals, long term care, home care, mental health) Other (specify in text box below)

53. Benefits

• Creates a process for pharmacy clinical documentation.
• Enables exchange of patient information related to medication management between a pharmacy provider and medical provider.
• Supports medication therapy management, medication adherence, medication optimization, electronic quality measurement, and care coordination to improve the quality of care for the patient. Supports the CMS Medicare Part D Enhanced Medicare Therapy Management (MTM) program that started on January 1, 2017.

54. Implementations/Case Studies

• Known implementers:
o BestRx
o DataScan
o Liberty Software
o Micro Merchant Systems
o PioneerRx
o QS/1
o Amplicare
o ComputerRx
o McKesson
o Rx30
o Azova
o DocsInk
o Pharmetika
o PrescribeWellness
o Strand
o AssureCare

• Organizations who sponsored the development of the specification:
o Community Care of North Carolina(CCNC)
o Pharmacy Health Information Technology (HIT) Collaborative
o National Community Pharmacy Association (NCPA) Innovation Center
o National Council for Prescription Drug Programs (NCPDP)

55. Development Background

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 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.
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). Please note, the FHIR Pharmacist Care Plan is published separately from this 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.