Transitions of care (MU3)
From OpenEMR Project Wiki
Revision as of 14:52, 24 February 2022 by Stephen Nielson (talk | contribs)
This document is part of our OpenEMR Certification Stage III Meaningful Use Documentation
Regulation Text
§ 170.315 (b)(1) Transition of care—
- Send and receive via edge protocol—
- Send transition of care/referral summaries through a method that conforms to the standard specified in § 170.202(d) and that leads to such summaries being processed by a service that has implemented the standard specified in § 170.202(a); and
- Receive transition of care/referral summaries through a method that conforms to the standard specified in § 170.202(d) from a service that has implemented the standard specified in § 170.202(a)(2).
- XDM processing. Receive and make available the contents of a XDM package formatted in accordance with the standard adopted in § 170.205(p)(1) when the technology is also being certified using an SMTP-based edge protocol.
- Validate and display —
- Validate C-CDA conformance – system performance. Demonstrate the ability to detect valid and invalid transition of care/referral summaries received and formatted in accordance with the standards specified in § 170.205(a)(3), (4), and (5) for the Continuity of Care Document, Referral Note, and (inpatient setting only) Discharge Summary document templates. This includes the ability to:
- Parse each of the document types.
- Detect errors in corresponding “document-templates,” “section-templates,” and “entry-templates,” including invalid vocabulary standards and codes not specified in the standards adopted in § 170.205(a)(3), (4), and (5).
- Identify valid document-templates and process the data elements required in the corresponding section-templates and entry-templates from the standards adopted in § 170.205(a)(3), (4), and (5).
- Correctly interpret empty sections and null combinations.
- Record errors encountered and allow a user through at least one of the following ways to:
- Be notified of the errors produced.
- Review the errors produced.
- Display. Display in human readable format the data included in transition of care/referral summaries received and formatted according to the standards specified in § 170.205(a)(3), (4), and (5).
- Display section views. Allow for the individual display of each section (and the accompanying document header information) that is included in a transition of care/referral summary received and formatted in accordance with the standards adopted in § 170.205(a)(3), (4), and (5) in a manner that enables the user to:
- Directly display only the data within a particular section;
- Set a preference for the display order of specific sections; and
- Set the initial quantity of sections to be displayed.
- Validate C-CDA conformance – system performance. Demonstrate the ability to detect valid and invalid transition of care/referral summaries received and formatted in accordance with the standards specified in § 170.205(a)(3), (4), and (5) for the Continuity of Care Document, Referral Note, and (inpatient setting only) Discharge Summary document templates. This includes the ability to:
- Create. Enable a user to create a transition of care/referral summary formatted in accordance with the standard specified in § 170.205(a)(3), (4), and (5) using the Continuity of Care Document, Referral Note, and (inpatient setting only) Discharge Summary document templates that includes, at a minimum:
-
- The data classes expressed in the standard in § 170.213 and in accordance with § 170.205(a)(4), (a)(5), and paragraphs (b)(1)(iii)(A)(3)(i) through (iii) of this section, or
- The Common Clinical Data Set in accordance with §170.205(a)(4) and paragraph (b)(1)(iii)(A)(3)(i) through (iv) of this section for the period until December 31, 2022, and
- The following data classes:
- Assessment and plan of treatment. In accordance with the “Assessment and Plan Section (V2)” of the standard specified in § 170.205(a)(4); or in accordance with the “Assessment Section (V2)” and “Plan of Treatment Section (V2)” of the standard specified in § 170.205(a)(4).
- Goals. In accordance with the “Goals Section” of the standard specified in § 170.205(a)(4).
- Health concerns. In accordance with the “Health Concerns Section” of the standard specified in § 170.205(a)(4).
- Unique device identifier(s) for a patient's implantable device(s). In accordance with the “Product Instance” in the “Procedure Activity Procedure Section” of the standard specified in § 170.205(a)(4).
- Encounter diagnoses. Formatted according to at least one of the following standards:
- The standard specified in § 170.207(i).
- At a minimum, the version of the standard specified in § 170.207(a)(4).
- Cognitive status.
- Functional status.
- Ambulatory setting only. The reason for referral; and referring or transitioning provider's name and office contact information.
- Inpatient setting only. Discharge instructions.
- Patient matching data. First name, last name, previous name, middle name (including middle initial), suffix, date of birth, address, phone number, and sex. The following constraints apply:
- Date of birth constraint.
- The year, month and day of birth must be present for a date of birth. The technology must include a null value when the date of birth is unknown.
- Optional. When the hour, minute, and second are associated with a date of birth the technology must demonstrate that the correct time zone offset is included.
- Phone number constraint. Represent phone number (home, business, cell) in accordance with the standards adopted in § 170.207(q)(1). All phone numbers must be included when multiple phone numbers are present.
- Sex constraint. Represent sex in accordance with the standard adopted in § 170.207(n)(1).
- Date of birth constraint.
-