Documenting and Sharing Care Plans for a Single Clinical Context

NCPDP - Comment

• Add the following:

Type-Implementation Specification

Standard Implementation/Specification- NCPDP Pharmacist eCare Plan Version 1.0: Guidance on the Use of the HL7 CDA Consolidated Templates for Clinical Notes R2.1 Care Plan

Standards Process Maturity – Final

Implementation Maturity- Production

Adoption Level – 2

Federally Required – No

Cost – $

Test Tool Availability – Yes

• Add the following:

Type-Implementation Specification

Standard Implementation/Specification- NCPDP HL7 CDA® R2 Implementation Guide: Pharmacist Care Plan Document, Release 1 - US Realm - US Realm

Standards Process Maturity – Final

Implementation Maturity- Production

Adoption Level – 2

Federally Required – No

Cost – $

Test Tool Availability – Yes

• Add the following:

Type-Implementation Specification

Standard Implementation/Specification- NCPDP HL7 CDA® R2 FHIR Implementation Guide: Pharmacist Care Plan Document, Release 1 - US Realm - US Realm

Comment: FHIR is used to implement the Care Plan. See https://www.healthit.gov/techlab/ipg/node/4/submission/1376

Standards Process Maturity – Final

Implementation Maturity- Pilot

Adoption Level – 1

Federally Required – No

Cost – $

Test Tool Availability – Yes

Care Plan Document Type is not Required

HL7 Implementation Guide for CDA® Release 2: Consolidated CDA Templates for Clinical Notes (US Realm), Draft Standard for Trial Use, Release 2.1. 

This should not be listed as required. MU2015 did not require the care plan document. MU2015 did require Concerns and Goals within transition of care documents but not specifically the Care Plan document. The snapshot or visit context of a care plan for transition of care is appropriate. A longitudinal care plan in the form of a CCDA is unwieldly and virtually useless from the perspective of a provider. The longitudinal care plan needs to be in the context of an application for optimal management and viewing.