1 / 6

S&I Framework – Transitions of Care Reference Implementation

S&I Framework – Transitions of Care Reference Implementation. Value Proposition For Using the Transitions of Care Reference Implementation For Consolidated CDA Validation, Consumption and Construction. Orginal Mission.

evadne
Download Presentation

S&I Framework – Transitions of Care Reference Implementation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. S&I Framework – Transitions of Care Reference Implementation Value Proposition For Using the Transitions of Care Reference Implementation For Consolidated CDA Validation, Consumption and Construction

  2. Orginal Mission 1. MUST deliver a way to read/write and validate ToC information packages (but not necessarily all supported content for all documents). 2. SHOULD deliver a way to read/write all supported content, but this may require diving down to a lower level of the API or writing raw XML. MUST deliver a high level API that allows for non-CDA experts to read and write ToC information. 3. High level API MUST be mappable to CIM for requirements traceability to ensure clinically relevant and valid data are exchanged. 4. MUST be model-driven, COULD use CIM model as the API target model. 5. MUST NOT be single platform or bias a particular platform. 6. MUST attract an ecosystem of customers -- including both end users and open source developers, with a reasonable total federal spend and a clear path to "revenue break even", where federal funding is not required.

  3. Features • Designed to use any Canonical Internal Model (CIM) (e.g. could support Green CDA) • Allows input and output of specification compliant CDA R2 and Consolidated CDA TOC Clinical Documents • Designed to support other near-isomorphic representations such as CCR, given extensions • Allows spec-compliant conversions between supported inputs, outputs and the CIM • Supports model driven specifications, so it avoids ambiguity and grey areas in interpretation of textual specifications like HL7 or IHE which are written with SHALLs and MAYs and subject to being construed in divergent ways by different readers.

  4. Features • Provides Validation of all inputs and output documents to spec conformance and returns XML based lists of validation warnings and/or errors if present. • Consumes XML based input and CIM models and produces XML based outputs • Generates a Java-based API for all specifications modeled (I.e. C32, CDA, CCD, CCCD, and TOC CIM). • Based on the Open Health Tools MDHT project.  Open Health Tools was formed by one of the founding members of the Eclipse Project and is currently under the stewardship of Dr. Robert Kolodner.

  5. How it can help Product Development • Provides simple interface for Consolidated CDA Validation • Implemented as a single Java library • Buildable in any platform via Maven • Can be extended to .NET with wrapping libraries • Runs in any J2EE container or Standalone

  6. Feedback • Replace original goals status of current state of development • Include a list of gaps with respect to the NPRM • Open the gaps to wide representation of audience to give balanced presentation • Advantages vs. Disadvantages

More Related