1 / 16

RC2I3 Proof of Concept

RC2I3 Proof of Concept. Broad Objectives. A choreography of services that proves the following: Services using HL7 RMIMs HL7 RIM based persistence Tolven RIM based backend Architecture Error handling Versioning Patterns – Order Management, QRL, others Security PODS. Time Targets.

shanna
Download Presentation

RC2I3 Proof of Concept

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. RC2I3 Proof of Concept

  2. Broad Objectives • A choreography of services that proves the following: • Services using HL7 RMIMs • HL7 RIM based persistence • Tolven • RIM based backend • Architecture • Error handling • Versioning • Patterns – Order Management, QRL, others • Security • PODS

  3. Time Targets • RC2I3 – 10/6/2010 • RC2 – 10/6/2010

  4. Deliverables • Referral with Tolven • Choreography 1 • Build CDA for referral • Choreography 2 • Order Management - Refer To • Order Management - Refer From • Outcomes • Choreography 3 • Mockup of outcomes analysis

  5. Referral Scenario • Refer From • Enter Allergies • Enter Medications • Create referral document • Send referral • Refer To • Receive referral • View referral document

  6. Outcomes Scenario • Measurement • Outcomes Measurement Services based on iSPY2 Data • Analysis • Outcomes Analysis Service that aggregates and computes Outcomes Measurements

  7. Areas

  8. Scripts • Referral Order • iSPY2 Outcomes

  9. Referral Overview

  10. Collect Information • The provider uses Tolven to submit information • Demographics • Allergies • Tolven is the application for use in providing all of this information • End to end support within Tolven

  11. Assemble and Validate CDA • The provider clicks the “Get Referral CDA” button • The CDA is presented to the provider • Tolven is the commissioner to the CDABuilder Service • CDABuilder Service is the commissioner to several services to get information • Tolven is service provider for • Demographics • Allergies • At least one other service (Lab, Medication List ) that is non Tolven is supported • CDA Builder validates information and transforms it as necessary • Tolven renders the returned document • Background tasks • Define “constrained” CDA; Define schema • Define Allergy Service Pim • Transform Allergy, Medication Lists to CDA • Expose Tolven Data via external service (Medication, Allergy, Demographics) • Choreography for pulling together CDA elements (as above + one or more non-Tolven Services) • Tolven must call CDABuilder service on vEHR • Tolven must render the CDA

  12. Submit Referral Order • Provider signs Referral • Submits Referral Order Request • Checks status of Referral Order • Tolven is the commissioner to the ReferralTo Service on the vEHR, which is exposed on the Order Request Manager (ORM) components • vEHR.ORM commissions to TolvenB instance of ReferTo representing the Refer To Physician • TolvenB is the commissioner to the vEHR.ORM via the ReferFrom Service interface to acknowledge the Order and accept • vEHR.ORM sets state of Referral to “Active(?)”, which Tolven can display • Background tasks • Tolven must wrap the CDA in the Referral Order • Tolven must call vEHR.ORM via Service Interfaces • vEHR.ORM must call Tolven via Service Interfaces (ReferFrom and ReferTo) • vEHR. ORM must handle transaction and state of the Order • Tolven will have to display transaction state

  13. Views Referral Order • Provider on Tolven B views the Referral Order on the other Tolven Instance • TolvenB renders the CDA Document • Background tasks • Tolven must render the CDA

  14. iSPY2 Outcomes Overview

  15. Collect Information • Tolven is used to collect information • Tolven is used end to end to support small pieces of outcome data • Tolven acts as the commissioner to some services for capturing information

  16. Assemble and Validate Outcomes Report • Provider can review report in Outcomes • Tolven is the commissioner to the OutcomesAnalysis Server • Input: PatientID • Output: Outcomes Analysis Report • Outcomes Analysis Service is commissioner to 2+ OutcomesMeasurement Services, retrieving information • OutcomesAnalysis processes some choreography over the information

More Related