1. H.1 Relied Upon Third Party
1.1. EDGE Protocol Interfaces (SMTP, etc)
2. Proctor Sheet: Requirements & Testing
2.1. Guides & Resources
2.1.1. FAQs on Drummond Customer Portal
2.1.2. ONC Certification Program Test Procedure
2.1.3. ONC Certification Program CCG
2.1.4. USCDI v3 Test Data Download
2.1.5. B.1 Edge Testing Tool (ETT)
2.1.6. C-CDA R.2.1 Message Validator for USCDI v3
2.1.7. ETT Testing Tool Support Group
2.1.8. ETT Testing Tool Supplemental Guide
2.1.9. Implementation Guide for Edge Protocols
2.1.10. Direct: Applicability Statement For Secure Health Transport
2.2. b.1.0: Test Readiness Confirmation & Setup
2.2.1. 1. Preload test data for Ambulatory and/or Inpatient settings.
2.2.2. 2. Successfully execute all applicable ETT test tool scenarios & test cases prior to the live test.
2.2.3. 3. Prior to testing, send all "Negative Test Case Results to Test Proctor.
2.2.4. 4. Proctor or the Developer may log into the Edge Testing Tool using the Vendor’s credentials to prevent the sharing of the SMTP username and password.
2.2.4.1. ETT Login
2.2.5. 5. Prior to the start of testing, Proctor has Developer verbally confirm Edge Protocol to be used to send/receive Transitions of Care.
2.3. b.1.2: SMTP - Receive using Edge Protocol
2.3.1. 1. Proctor confirms the Developer is performing the ETT (b)(1) Certification tests.
2.3.2. 2. Proctor confirms the Developer is using TLS or has demonstrated the use of a secure connection.
2.3.2.1. Tool: SSL Server Test
2.3.2.1.1. Screen1: Overall
2.3.2.1.2. Screen2" TLS
2.3.3. 3. Developer selects the “Receive using Edge Protocol – SMTP” option using the profile and TLS previously confirmed.
2.3.3.1. SMTP Receive Profile
2.3.4. 4. Developer uses SMTP Test 9,16,20 to select and RECEIVE each of the C-CDA Document Type payloads for the (b)(1) setting being certified from the ETT to the SUT:
2.3.4.1. SMTP Test 9,16,20
2.3.4.1.1. Select SVAP for USCDIv3
2.3.5. 5. Developer uses SMTP Test 9,16,20 to select and RECEIVE the XDM document payloads from the ETT to the SUT (i)(C): - Limited Metadata - Full Metadata
2.3.5.1. Two XDM Files to Receive
2.3.6. 6. Developer uses SMTP Test 9,16,20 to RECEIVE each of the Negative Test Case USCDI payloads to the SUT to process (ii)(A)(2),(5)
2.3.6.1. Negative Test Case Files
2.3.6.1.1. Example: Using the Message Valdiator to see expected errors.
2.3.7. 7. Developer uses SMTP Tests 25(a)–(f) RECEIVE C-CDA attachment and a C-CDA within the XDM package as payloads to the SUT to process.
2.3.7.1. Receiving Multiple Attachments
2.3.7.1.1. XDM File Format
2.3.8. 8. Developer uses SMTP Tests 26-27 to RECEIVE C-CDA documents/XDM package with the following style sheet/header issues for the SUT to process:
2.3.8.1. Screen Shot1
2.3.9. 9. Developer uses SMTP Tests 28-29 to send XDM packages with different MIME Types:
2.3.9.1. Screen Shot1
2.4. b1.6: (Alternative ) SMTP with POP3 - Receive Using Edge Protocol
2.5. b1.7: (Alternative ) SMTP with IMAP - Receive Using Edge Protocol
2.6. b.1.1: Validate & Display (after SMTP Receive)
2.6.1. 1.Developer provides evidence that each of the C-CDA Document Type payloads receive by the SUT can:
2.6.1.1. Parse and process valid document templates and required data elements.
2.6.1.2. Display human readable view for all require d USCDI elements, document header, and narrative text
2.6.1.3. Display section views (and document header information)
2.6.1.4. Display data from particular sections
2.6.1.5. Set preference for order of specific sections
2.6.1.6. Set initial quantity of sections for display
2.6.2. 2. Developer provides evidence that each of the Negative Test Case for USCDI payloads sent to the SUT processes correctly
2.6.2.1. Using ETT Message To Emulate Validation
2.6.2.1.1. Screenshot1
2.6.2.1.2. Screenshot2
2.6.2.1.3. Screenshot3
2.6.3. 3. For SMTP-based Protocols ONLY Developer provides evidence that all of the XDM document payloads received by the SUT can be properly processed (i)(C).
2.6.3.1. XDM Format
2.6.3.2. XDM Content
2.6.3.2.1. SUBSET01
2.7. b.1.3: SMTP - Create/Send Using Edge Protocol
2.7.1. 1. Proctor confirms the Developer is performing the ETT (b)(1) Certification tests. (ALREADY CONFIRMED)
2.7.2. 2. Proctor confirms the Developer is using TLS or has demonstrated the use of a secure connection. (ALREADY CONFIRMED)
2.7.2.1. Tool: SSL Server Test
2.7.3. 3. Developer selects the “Send using Edge Protocol – SMTP” option using the profile and TLS previously confirmed.
2.7.3.1. Send with TLS
2.7.4. 4. Developer uses SMTP Test 8 and 14 to verify the ability of the SUT to send an email to the ETT using the SMTP protocol with STARTTLS and PLAIN SASL Authentication (if enabled).
2.7.4.1. PASS Example
2.7.5. 5. All of the following C-CDA Release 2.1 Document Template Types must be sent by the SUT to the ETT where the Developer selects SMTP Test 18 to receive:
2.7.5.1. 5.1 Select the Test Case File
2.7.5.1.1. RUN to wait for SUT message
2.7.5.2. 5.2 Validate with Message Validator
2.7.5.2.1. Errors and Warnings
2.7.6. 6. Developer selects the “Send using Edge Protocol – Delivery Notification” using the profile and TLS previously confirmed.
2.7.6.1. Screenshot1
2.7.7. 7. Developer uses SMTP MT Test 46 (Generate Disposition Notification Options Header) to verifies the ability of the sending system to send messages with a correct Disposition Notification Options Header.
2.7.7.1. Screenshot1
3. What are the TOC Documents and Required USCDI Classes (sections) / Elements?
3.1. What are the TOC Documents and Required USCDI Classes (sections) / Elements?
3.1.1. HL7 R2.1 Continuity of Care (CCD) : Ambulatory & Inpatient
3.1.1.1. Header
3.1.1.2. Sections
3.1.2. HL7 R2.1 Referral Note (RN) : Ambulatory & Inpatient
3.1.2.1. Header
3.1.2.2. Sections
3.1.3. HL7 R2.1 Discharge Summary (DS) : Inpatient
3.1.3.1. Header
3.1.3.2. Sections
3.2. Analysis Process
3.2.1. Review Required C-CDA Document Sections/elements
3.2.1.1. HL7 Templates Implementation Guide
3.2.2. Map C-CDA Sections/Fields to USCDIv3 (v2, v1) Classes/Elements
3.2.2.1. USCDI v3 Specification
3.2.3. Identify Required C-CDA Sections/Fields NOT found in USCDI: Gap Analysis
3.2.3.1. HL7 Templates Implementation Guide
3.2.4. Identify Missing Database Tables/Elements: Gap Analysis
3.2.5. Identify Missing UI Screens/Fields: Gap Analysis
3.3. HL7 Companion Guide: Mapping USCDI Classes/Elements to C-CDA Sections/Fields
3.3.1. Required Non-USCDI Elements
3.3.2. Special USCDI Requirements Table: Examples
3.3.2.1. USCDIv3
3.3.2.2. USCDIv2
4. b.1 relationship to b.2
4.1. b.1.2: SMTP or POP3 - TOC Receive
4.1.1. b.1.1: Validate & Display
4.1.1.1. Change Status to "Validated" In Received TOC's (suggested workflow)
4.1.1.1.1. b.2 Clinical Reconciliation
5. b.1 relationship to g.2
5.1. b.1.3: SMTP - Create/Send
5.1.1. g.2 Measure Calculation
5.1.1.1. RT7 Electronic Referral Loops
5.1.1.1.1. Denominator = Number of CCD's Created in Reporting Period
5.1.1.1.2. Numerator = Number if CCD's in Denominator Sent in Reporting Period
6. Design / Implementation Considerations
6.1. Create TOC Docs
6.1.1. Send TOC C-CDA Docs
6.1.1.1. EDGE Protocol Transmit
6.2. Display TOC Docs
6.2.1. Validate TOC Docs
6.2.1.1. Store Received TOC Docs
6.2.1.1.1. EDGE Protocol Receive