Source: https://www.healthit.gov/test-method/care-plan
Timestamp: 2019-04-26 10:44:26+00:00

Document:
Enable a user to record, change, access, create, and receive care plan information in accordance with the Care Plan document template, including the Health Status Evaluations and Outcomes Section and Interventions Section (V2), in the standard specified in §170.205(a)(4).
Please consult the Final Rule entitled: 2015 Edition Health Information Technology (Health IT) Certification Criteria, 2015 Edition Base Electronic Health Record (EHR) Definition, and ONC Health IT Certification Program Modifications for a detailed description of the certification criterion with which these testing steps are associated. We also encourage developers to consult the Certification Companion Guide in tandem with the test procedure as they provide clarifications that may be useful for product development and testing.
Note: The order in which the test steps are listed reflects the sequence of the certification criterion and does not necessarily prescribe the order in which the test should take place.
Using the ETT: Message Validators – C-CDA R2.1 Validator, the health IT developer downloads the ONC-supplied data instructions through the sender download selections of the “170.315_b9_CP_Amb” or “170.315_b9_CP_Inp” criteria and one of the care plan instruction documents and executes the download.
Using the ONC-supplied care plan instruction document returned in step 1, a user enters the care plan information into the Health IT Module.
Based on the health IT setting(s) to be certified, a user repeats steps 1-3 for each of the ambulatory and/or inpatient care plan instruction documents found in the ETT: Message Validators. The recording of a care plan is required for all of the care plan instruction documents for a given health IT setting.
For each care plans recorded by the SUT, the tester verifies that the outlined care plan information has been recorded correctly and without omission through visual inspection of the SUT using the ONC-supplied care plan instruction document associated with the recorded care plan.
The tester verifies that care plan information can be accessed and changed using visual inspection of the SUT.
For each care plan document created in step 1, the user submits the care plan document to the tester for verification.
Using the ETT: Message Validators – C-CDA R2.1 Validator, the tester uploads the submitted care plan (xml file) created by the Health IT Module in step 1 of the SUT, through the sender upload selection of the “170.315_b9_CP_Amb” or “170.315_b9_CP_Inp” criteria and file name of the care plan recorded by the SUT, and executes the upload of the submitted file to the ETT: Message Validators.
The tester uses the Validation Report produced by the ETT: Message Validators in step 1 to verify the validation report indicates passing without error to confirm that the care plan is a C-CDA R2 Release 2.1 document conformant to the standard specified at § 170.205(a)(4) and includes the Health Status Evaluations and Outcomes Section and Interventions Section (V2).
As required by the ONC-supplied care plan instructions with the corresponding file names as uploaded in step 1, the tester uses the ONC-supplied care plan document and the ETT: Message Validators Message Content Report to verify the additional checks for equivalent text for the content of all section level narrative text.
Using the ETT: Message Validators - C-CDA R2.1 Validator, the health It developer downloads the ONC-supplied care plan xml documents through the receiver download selections of the “170.315_CP_Amb” or “170.315_CP_Inp” criteria and care plan xml file and executes the download of the care plan xml file.
Based upon the health IT setting(s) to be certified, a user repeats steps 1-2 for each ambulatory and/or inpatient care plan (xml) document in the ETT: Message Validators. All of the care plan (xml) documents for a given health IT setting must be received.
Using the ETT: Message Validators – C-CDA R2.1 Validator, the health It developer downloads the ONC-supplied care plan negative test xml documents through the receiver download selections of the “NegativeTesting CarePlan” criteria and one of the invalid C-CDA documents and executes the download of the invalid C-CDA xml file.
Using the Health IT Module, the user receives the applicable C-CDA document types containing errors in the corresponding “document-templates,” “section-templates,” and “entry-templates” including invalid vocabulary standards and codes not specified in the standards adopted in at § 170.205(a)(4) HL7 Implementation Guide for CDA® Release 2: Consolidated CDA Templates for Clinical Notes, DSTU Release 2.1 and reports the errors.
A user repeats steps 4-5 for each of the negative test samples in ETT: Message Validators “NegativeTesting_CarePlan.” All of the negative test care plan (xml) documents must be received.
The tester creates a human readable version of the care plan document downloaded in step 1 of the SUT to be used for verification.
For each care plan document received, the tester verifies that the Health IT Module can receive a care plan document formatted in accordance with the standard specified at § 170.205(a)(4) and includes the Health Status Evaluations and Outcomes Section and Interventions Section (V2) using visual inspection.
Using the Health IT Module, the tester verifies that the care plan document received in step 2 is accurate and without omission through the visual inspection.
Added clarifications that Consolidated CDA creation performance is required for this certification criterion per the 2015 Edition final rule Correction Notice.
Added clarification about the data expected in the “Goals” and “Health Concerns” Sections.
Added clarification that Health IT Modules are not required to enable a user to reconcile received care plan data.
Provides notification of March 2017 Validator Update of C-CDA 2.1 Corrections adoption and compliance requirements for the entire criterion.
Provides notification of April 2018 Validator Update of C-CDA 2.1 Corrections adoption and compliance requirements for the entire criterion. Note: Due to an error in calculation ONC is also updating the dates for compliance with the March 2017 Validator Update of C-CDA 2.1 Corrections that were adopted September 29, 2017.
Provides notification of August 2018 Validator Update of C-CDA 2.1 Corrections adoption and compliance requirements for the entire criterion.
This Certification Companion Guide (CCG) is an informative document designed to assist with health IT product development. The CCG is not a substitute for the 2015 Edition final regulation. It extracts key portions of the rule’s preamble and includes subsequent clarifying interpretations. To access the full context of regulatory intent please consult the 2015 Edition final rule or other included regulatory reference. The CCG is for public use and should not be sold or redistributed.
Privacy and Security: This certification criterion was adopted at § 170.315(b)(9). As a result, an ONC-ACB must ensure that a product presented for certification to a § 170.315(b) “paragraph (b)” criterion includes the privacy and security criteria (adopted in § 170.315(d)) within the overall scope of the certificate issued to the product.
The privacy and security criteria (adopted in § 170.315(d)) do not need to be explicitly tested with this specific paragraph (b) criterion unless it is the only criterion for which certification is requested.
As a general rule, a product presented for certification only needs to be tested once to each applicable privacy and security criterion (adopted in § 170.315(d)) so long as the health IT developer attests that such privacy and security capabilities apply to the full scope of capabilities included in the requested certification. However, exceptions exist for § 170.315(e)(1) “VDT” and (e)(2) “secure messaging,” which are explicitly stated.
For each applicable P&S certification criterion not certified for approach 1, the health IT developer may certify for the criterion using system documentation which provides a clear description of how the external services necessary to meet the P&S criteria would be deployed and used. Please see the 2015 Edition final rule correction notice at 80 FR 76870 for additional clarification.
Design and Performance: The following design and performance certification criteria (adopted in § 170.315(g)) must also be certified in order for the product to be certified.
When a single quality management system (QMS) is used, the QMS only needs to be identified once. Otherwise, the QMS’ need to be identified for every capability to which it was applied.
When a single accessibility-centered design standard is used, the standard only needs to be identified once. Otherwise, the accessibility-centered design standards need to be identified for every capability to which they were applied; or, alternatively the developer must state that no accessibility-centered design was used.
C-CDA creation performance (§ 170.315(g)(6)) does not need to be explicitly tested with this criterion unless it is the only criterion within the scope of the requested certification that includes C-CDA creation capabilities. Note that the application of § 170.315(g)(6) depends on the C-CDA templates explicitly required by the C-CDA-referenced criterion or criteria included within the scope of the certificate sought. Please refer to the C-CDA creation performance Certification Companion Guide for more details.
Technical outcome – A user can record, change, access, create, and receive care plan information according to the Care Plan document template in the HL7 Implementation Guide for CDA® Release 2: Consolidated CDA Templates for Clinical Notes (US Realm), Draft Standard for Trial Use Release 2.1, including the Health Status Evaluations and Outcomes Section and Interventions Section (V2).
Consistent with ONC policy, health IT must enable a user to record, change, access, create, and receive information for those sections of the C-CDA Care Plan template that are required, including the “Goals” and “Health Concerns” Sections. [see also 80 FR 62648] We would expect that these sections could contain patient-expressed information, including patient-expressed goals and health concerns. Because of this, the information contained within the “Goals” and “Health Concerns” Sections of the care plan document could differ from the information contained within those same sections in a transition of care/referral summary document.
In order to mitigate potential interoperability errors and inconsistent implementation of the HL7 Implementation Guide for CDA® Release 2: Consolidated CDA Templates for Clinical Notes, Draft Standard for Trial Use, Release 2.1, ONC assesses, approves, and incorporates corrections as part of required testing and certification to this criterion. [see FAQ #51] Certified health IT adoption and compliance with the following corrections are necessary because they implement updates to vocabularies, update rules for cardinality and conformance statements, and promote proper exchange of C-CDA documents. Consistent with FAQ 51, there is a 90-day delay from the time the CCG has been updated with the ONC-approved corrections to when compliance with the corrections will be required to pass testing (i.e., C-CDA 2.1 Validator). Similarly consistent with FAQ 51, there will be an 18-month delay before a finding of a correction’s absence in certified health IT during surveillance would constitute a non-conformity under the Program.

References: §170
 § 170
 § 170
 § 170
 § 170
 § 170
 § 170
 § 170
 § 170
 § 170
 § 170
 § 170