F.4.2 CONNECT SAML Assertions SAML assertions for transactions with CMS must conform to the for Health “Implementation Information Handlers for Electronic Submission of Medical Documentation Project,” Section 5.3.5.5: esMD SAML Assertions Details, which states: The CONNECT SAML Assertions define the exchange of metadata used to characterize the initiator of a request so that it may be evaluated by the Payer Gateway in local authorization decisions. The purpose of this SAML Assertion exchange is to provide the Payer Gateway with the information needed to make an authorization decision using the policy enforcement point for the requested esMD function. Each initiating SOAP message must convey information regarding the Registration Requestor’s attributes and authentication using SAML 2.0 Assertions. SAML assertions for transactions with Commercial Payers must conform to the eHealth Exchange Authorization Framework Specification v3.0. F.4.3 IHE XD* Metadata Systems using an HPD Plus DSMLv2 document payload over CONNECT or Direct should adopt the IHE Cross Enterprise Document Reliable Interchange (XDR) profile with XDS Repository Submission Request Provide and Register Document set b (ITI-41) transaction metadata. – Cross-Enterprise Document Reliable Interchange (XDR) provides document interchange using a reliable messaging system. This permits direct document interchange between EHRs, PHRs, and other healthcare IT systems in the absence of a document sharing infrastructure such as XDS Registry and Repositories. Cross-Enterprise Document Media Interchange (XDM) provides document interchange using a common file and directory structure over several standard media, including email. This permits the use of email to convey documents. XDM defines no new metadata but leverages the existing XDS metadata. F.5 Overview of a Payload Over CONNECT with XDR This section defines how a transaction may be sent over CONNECT with the eHealth Exchange CAQH CORE X12 Document Submission Service Interface Specification. Figure 13: CONNECT w/ ASC X12N 275 Note: Per specifications, encoding for XDR may be indicated in the metadata, and encoding must be Base64.
F.4.2 CONNECT SAML Assertions SAML assertions for transactions with CMS must conform to the “Implementation for Health Information Handlers for Electronic Submission of Medical Documentation Project,” Section 5.3.5.5: esMD SAML Assertions Details, which states: The CONNECT SAML Assertions define the exchange of metadata used to characterize the initiator of a request so that it may be evaluated by the Payer Gateway in local authorization decisions. The purpose of this SAML Assertion exchange is to provide the Payer Gateway with the information needed to make an authorization decision using the policy enforcement point for the requested esMD function. Each initiating SOAP message must convey information regarding the Registration Requestor’s attributes and authentication using SAML 2.0 Assertions. SAML assertions for transactions with Commercial Payers must conform to the eHealth Exchange Authorization Framework Specification v3.0. F.4.3 IHE XD* Metadata Systems using an HPD Plus DSMLv2 document payload over CONNECT or Direct should adopt the IHE Cross Enterprise Document Reliable Interchange (XDR) profile with XDS Repository Submission Request Provide and Register Document set – b (ITI-41) transaction metadata. Cross-Enterprise Document Reliable Interchange (XDR) provides document interchange using a reliable messaging system. This permits direct document interchange between EHRs, PHRs, and other healthcare IT systems in the absence of a document sharing infrastructure such as XDS Registry and Repositories. Cross-Enterprise Document Media Interchange (XDM) provides document interchange using a common file and directory structure over several standard media, including email. This permits the use of email to convey documents. XDM defines no new metadata but leverages the existing XDS metadata. F.5 Overview of a Payload Over CONNECT with XDR This section defines how a transaction may be sent over CONNECT with the eHealth Exchange CAQH CORE X12 Document Submission Service Interface Specification. Figure 13: CONNECT w/ ASC X12N 275 Note: Per specifications, encoding for XDR may be indicated in the metadata, and encoding must be Base64.
CDAR2_AIG_CCDA_EXCHANGE_R1_D1_2016MAY%20V2%20Typo%20Corrections%20clean.docx