1 / 20

Cross-Paradigm Interoperability Implementation Guide for Immunizations (“X Paradigm”)

Cross-Paradigm Interoperability Implementation Guide for Immunizations (“X Paradigm”). Service Oriented Architecture May 2012. Project Scope.

jafari
Télécharger la présentation

Cross-Paradigm Interoperability Implementation Guide for Immunizations (“X Paradigm”)

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. Cross-Paradigm Interoperability Implementation Guide for Immunizations(“X Paradigm”) Service Oriented Architecture May 2012

  2. Project Scope “This implementation guide will explore the Service-Aware Interoperability Framework (SAIF) methodology to show how various HL7, IHE and OMG immunization-related artifacts can be deployed to satisfy immunization interoperability use cases. “

  3. January – May 2012 • Determined approach • What artifacts to use • What form the document takes • “Venn Diagrams” – overlap among artifacts • Mapped relevant artefacts to outline section • Documented artefact spec documents • Recruit case studies • Vet work so far • Determined similarities with Semantic Health Net project

  4. Project Sections • Layered Service Architecture • Use Cases • Case Studies • Platform Independent Model • Common behavioural model • Common information model • Solution Architecture • Relation to SAIF

  5. Scope Refinement • Drools out of scope • FHIR out of scope (for now) • SBVR (“Semantics of Business Vocabulary and Rules”) added • Others to be considered as solution develops

  6. Common Information Model • Approach • Monitor and build off CCDA • Start with V2-CCDA and V2-IC comparison • Add EHR FIM information model , IZ DAM, vMR • Template challenges

  7. CDS • Arden, GELLO • Collect existing examples • Arden • Translate RulesSpeak into Arden • GELLO • IG for vMR • Extract sample rules from CDC project, implement • Determine fit of Arden and GELLO into DSS and overall architecture

  8. Project wiki page http://hssp.wikispaces.com/Cross+Paradigm+Interoperability+Implementation+Guide+for+Immunization

  9. New Discussion • Layered Service Architecture • Begin a graph with the various paths through the various Platform Specific Model choices • Gerry to mock up diagram from white board drawing

  10. Slides from January 2012

  11. CDS notes • Is the assumption that SOA is the vehicle • Set forth assumptions • Will this discuss GELLO or ARDEN rules and import them?

  12. SAIF Arch Prog Notes • Is FHIR intended to serve as a Common Information Model in a SOA/SAIF contest to which multiple other HL7 and non-HL7 artifacts can be mapped? • Yes • Devil is in the details • Look at the conformance statements in SAIF CD • These are aimed at what the SAIF implementation guide should do, not something following the SAIF IG

  13. Some Ideas • Look at the conformance statements in SAIF CD • Create a mapping including FHIR and including Rob S’s list of data elements and mapping other artifacts into it. I.e. map everything to FHIR common data model. • Examine “use case“ artifacts to see what use cases can be implemented within the scope of the project • Revisit IXS, RLUS and DSS. Make list of needed PSMs. Map services to PSMs • Should lend itself to a tool • Be part of MnM BOF for EA – see Patrick • Be part of Out of cycle meeting to work on artifacts for SAIF IG - TBD

  14. SOA Ideas • Can break into 2 parts, • high level – scoping, approach, requirements • Technical framework – SAIF IG • Avoid dependencies on unfinished specs • Context in services is established thru service contract (in layers)

  15. What the project is • A roadmap to establishing interoperability among a multiplicity of systems speaking different (immunization) standards • Lends itself to tooling • Provide a standards guide that addresses multiple “hops” in the communication path • Be implementable and testable • Allows domain experts to trace use cases to implementation

  16. What the project is not • Does not change existing specs • Does not recommend one spec over another • Exception: may change or recommend service tech specs • S&I does gap analysis • Prefer not to recommend

  17. Straw man outline • Standards to include - examples • HL7 V2 IZ IGs • IHE Immunization Content/XDS/XCA • IXS, RLUS, DSS, • CTS2….tbd • Common Information Model

  18. Project Phases • Project Approach • Deliverable

  19. Fri Q1 ideas • Project Scope – “explore” vs “show” also remove “methodology” • JD will assist organizing next OMG tech mtg • A way to gain visibility to OMG working drafts • New mechanism for HL7 members – research • Include webexes at OMG, HL7 and IHE • SAIF Arch Prog Out-of-cycle • Coordinate with S&I Framework • Make community initiative, not PH – Ken • Coordinate with Aus PCEHR project • Roles and control

  20. Fri Q1 ideas cont • hDATA may provide data model • Talk to Gerry and Lloyd • The issue of synchronous vs. asynchronous transactions is out of scope and implementation decision • Clearly state that the expected result is to add PSMs to existing tech specs and tweak tech specs • What formalism? SoaML? SOA ref arch framework?

More Related