Presentation on theme: "CDA for HAI Reporting January 2007 Update. Project Outline Deliverables –Sample instances BSI, SSI, Denominator for Procedure, Denominiator for ICU –Stylesheets."— Presentation transcript:
Project Outline Deliverables –Sample instances BSI, SSI, Denominator for Procedure, Denominiator for ICU –Stylesheets Narrative block population Online display –Implementation guides One generic guide (common header, high level common details) Lightweight specific guides for each form. –CDA utilities Database loading Validation –Training materials
Project Outline (continued) Events –CDA challenge More later… –Face to face meeting (tenative: mid Feb) Review draft implementation guides Start ballot preparation
Current Status Samples instances –BSI numerator and ICU denominator ready for review. –Other forms need more work. Transforms –Narrative block population and display stylesheets for BSI numerator and ICU denominator ready for review. –Other forms not yet started (but will leverage existing work; degree of customization TBD). Implementation guides –Outline of the generic guide started Everything else –Not yet…
CDA Challenge Overview Purpose –Give vendors an trial run at implementing CDA for HAI Create CDA instances based on the preliminary implementation guides Submit them to a validating website –Provides real time feedback to implementors –Helps identify areas of difficulty in the specification (may need further documentation, examples, etc.) –Discuss results Vendors can present lessons learned at the F2F meeting.
CDA Transformations Narrative block transform –Starts with a CDA with no narrative block. –Creates narrative content from the entries. Display stylesheet –Mimics the look of the printed forms. –Displays results, not for data capture. –Works from the results of the narrative block transform. Demonstration…
Interesting Issues OID Management –Some OIDs managed by submitters, others by NHSN. How do we handle this effectively? –Substantial overlap with another CDC reporting projects (NAACCR). –The OID manager in PHIN-VADS looks like a good solution. Confidentiality –Need separate codes for patient identifiable and aggregate data N for normal, A for aggregate? Template ID expiration –HAI forms have an OMB number (we will store this in a template id), which has an expiration date. Can/should this be represented in the instance? Terminology –NHSN codes are being used almost exclusively for the pilot. –Where NHSN codes do not exist (section codes, etc.) should new NHSN codes be created, or should we submit requests to LOINC? Use of XD*-LAB –Uses, but ISLT is not an allowable value in the CDA XML schema (fixed to SPEC).
Your consent to our cookies if you continue to use this website.