CROWNWeb – 3 rd Party Submit

1. CROWNWeb – 3rd Party Submit • Matt McDonoughCommunications CoordinatorNW7

2. 3rd Party Submit - Overview • Known as “EDI” in CROWNWeb – Electronic Data Interchange • Currently available only to LDOs (Fresenius, Davita, DCI) • Only users with appropriate Role and Scope (remember that?) can access EDI functionality in CROWNWeb • Limited to Patient Information – No facility info

3. The Actors • LDOs – Create batch file, upload to CROWNWeb • Facilities – Responsible* for batch submitted data (correcting near matches, incorrect data, etc.) • Networks – Assist in resolution of problems Facilities may experience *unofficially – recommended by QIG

4. The Data • An uploaded EDI file may contain: • Patient ID information • Admit/Discharge • Modality and treatment information • Vascular access • Clinical lab data • Maintains ESRD patient registry • Provides CPM data to CMS

5. The Format • XML format • Verified by an XSD (XML Schema Definition) tool – Ensures compliance with required data format • Header defines how the data will be interpreted • References W3.org XML standards.

6. Submitting in CROWNWeb • Users click on the EDI link on the main CROWNWeb page. • Users click on the “File Upload” link on the EDI page. • Users click “Browse” and find the file they want to upload. • Users click “Upload” to send the file to CROWNWeb.

7. 3rd Party Submit – Data Flow 1 • XML file is created and submitted by LDO • CROWNWeb validates syntax (schema) of data – Once accepted, processing can begin • XSD file ensures all required elements in the submitted file are present

8. 3rd Party Submit – Data Flow 2 • Matching logic enacted: • Exact match – Validated and appended to patient data (if patient exists in the facility) or creates admit for the patient (if not at the facility) • Near match – Flagged for resolution – Validated when resolved • No match – Validates data elements for new patient • Stores records (new or updated) in CROWNWeb

9. 3rd Party Submit – Errors • If errors are encountered during validation: • Errors are noted in error table • Appropriate parties notified • Data errors resolved according to CMS policy

10. An Example EDI File • This iswhat thedata lookslike…

11. 3rd Party Submit – The Future • The goal is to make EDI available to all capable ESRD entities (MDOs, SDOs, independent facilities, vendors/labs, etc.)

12. Next Call… April 28thBy special request… Reporting • How is reporting done? • Reporting capabilities now • Reporting in future releases

13. Thanks! • Matt McDonoughmmcdonough@nw7.esrd.net