DS4P+Feedback+to+Meaningful+Use+Stage+3+RFC

include component="page" wikiName="siframework" page="Data Segmentation Header" =Please review the HITPC Meaningful Use Request for Comment. You can provide feedback directly to the HIT Policy Committee [|here.] =

Review the RFC:
HITPC RFC for Meaningful Use Stage 3

IEWG101 - Page 27 of RFC

 * **MENU objective:** For patients transitioned without a care summary, an individual in the practice should query an outside entity. The intent of this objective is to recognize providers who are proactively querying.
 * **Certification criteria:**The EHR must be able to query another entity for outside records and respond to such queries. The outside entity may be another EHR system, a health information exchange, or an entity on the NwHIN Exchange, for example. This query may consist of three transactions:
 * Patient query based on demographics and other available identifiers, as well as the requestor and purpose of request.
 * Query for a document list based for an identified patient
 * Request a specific set of documents from the returned document list
 * When receiving inbound patient query, the EHR must be able to:
 * Tell the querying system whether patient authorization is required to retrieve the patient’s records and where to obtain the authorization language*. (E.g. if authorization is already on file at the record-holding institution it may not be required).
 * At the direction of the record-holding institution, respond with a list of the patient’s releasable documents based on patient’s authorization
 * At the direction of the record-holding institution, release specific documents with patient’s authorization
 * The EHR initiating the query must be able to query an outside entity* for the authorization language to be presented to and signed by the patient or her proxy in order to retrieve the patient’s records. Upon the patient signing the form, the EHR must be able to send, based on the preference of the record-holding institution, either:
 * A copy of the signed form to the entity requesting it
 * An electronic notification attesting to the collection of the patient’s signature
 * //*Note:// The authorization text may come from the record-holding EHR system, or, at the direction of the patient or the record-holding EHR, could be located in a directory separate from the record-holding EHR system, and so a query for authorization language would need to be directable to the correct endpoint.

MU04 - Page 29 of RFC

 * Some federal and state health information privacy and confidentiality laws, including but not limited to 42 CFR Part 2 (for substance abuse), establish detailed requirements for obtaining patient consent for sharing certain sensitive health information, including restricting the recipient’s further disclosure of such information.
 * How can EHRs and HIEs manage information that requires patient consent to disclose so that populations receiving care covered by these laws are not excluded from health information exchange?
 * How can MU help improve the capacity of EHR infrastructure to record consent, limit the disclosure of this information to those providers and organizations specified on a consent form, manage consent expiration and consent revocation, and communicate the limitations on use and restrictions on re-disclosure to receiving providers?
 * Are there existing standards, such as those identified by the Data Segmentation for Privacy Initiative Implementation Guide, that are mature enough to facilitate the exchange of this type of consent information in today’s EHRs and HIEs?

media type="custom" key="21882180"

media type="custom" key="21882176" 
 * MENU ** objective: For patients transitioned without a care summary, an individual in the practice should query an outside entity. The intent of this objective is to recognize providers who are proactively querying.

** Certification criteria: ** The EHR must be able to query another entity for outside records and respond to such queries. The outside entity may be another EHR system, a health information exchange, or an entity on the NwHIN Exchange, for example. This query may consist of three transactions: Patient query based on demographics and other available identifiers, as well as the requestor and purpose of request. Query for a document list based for an identified patient Request a specific set of documents from the returned document list When receiving inbound patient query, the EHR must be able to: Tell the querying system whether patient authorization is required to retrieve the patient’s records and where to obtain the authorization language*. (E.g. if authorization is already on file at the record-holding institution it may not be required). At the direction of the record-holding institution, respond with a list of the patient’s releasable documents based on patient’s authorization At the direction of the record-holding institution, release specific documents with patient’s authorization The EHR initiating the query must be able to query an outside entity* for the authorization language to be presented to and signed by the patient or her proxy in order to retrieve the patient’s records. Upon the patient signing the form, the EHR must be able to send, based on the preference of the record-holding institution, either: A copy of the signed form to the entity requesting it An electronic notification attesting to the collection of the patient’s signature //*Note:// The authorization text may come from the record-holding EHR system, or, at the direction of the patient or the record-holding EHR, could be located in a directory separate from the record-holding EHR system, and so a query for authorization language would need to be directable to the correct endpoint.

include component="page" wikiName="siframework" page="Data Segmentation for Privacy Initiative Contacts" include component="page" wikiName="siframework" page="space.template.inc_contentleft_end"