Presentation on theme: "CROWNWeb 3 rd Party Submit CROWNWeb – 3 rd Party Submit Matt McDonough Communications Coordinator NW7."— Presentation transcript:
CROWNWeb 3 rd Party Submit CROWNWeb – 3 rd Party Submit Matt McDonough Communications Coordinator NW7
CROWNWeb 3 rd Party Submit 3 rd 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
CROWNWeb 3 rd Party Submit 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
CROWNWeb 3 rd Party Submit 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
CROWNWeb 3 rd Party Submit 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.
CROWNWeb 3 rd Party Submit 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.
CROWNWeb 3 rd Party Submit 3 rd Party Submit – Data Flow 1 1. XML file is created and submitted by LDO 2. CROWNWeb validates syntax (schema) of data – Once accepted, processing can begin 3. XSD file ensures all required elements in the submitted file are present
CROWNWeb 3 rd Party Submit 3 rd Party Submit – Data Flow 2 4. 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 5. Stores records (new or updated) in CROWNWeb
CROWNWeb 3 rd Party Submit 3 rd 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
CROWNWeb 3 rd Party Submit An Example EDI File This is what the data looks like…
CROWNWeb 3 rd Party Submit 3 rd Party Submit – The Future The goal is to make EDI available to all capable ESRD entities (MDOs, SDOs, independent facilities, vendors/labs, etc.)
CROWNWeb 3 rd Party Submit Next Call… April 28 th By special request… Reporting How is reporting done? Reporting capabilities now Reporting in future releases
CROWNWeb 3 rd Party Submit Thanks! Matt McDonough email@example.com firstname.lastname@example.org