1 / 5

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

Cross-Paradigm Interoperability Implementation Guide for Immunizations (“X Paradigm”). Service Oriented Architecture Baltimore 2012. Open Issues. How to deal with realm-specific variations? E.g. VIS statements

aletta
Download Presentation

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 Baltimore 2012

  2. Open Issues • How to deal with realm-specific variations? E.g. VIS statements • Whether to include VIS and adverse event reporting (may flesh out as other artefacts considered). • Link to IZ DAM is to ballot version, not published version (which requires login) • What is the standard interface when an IIS calls a remote decision support service to fill in forecast fields of RSP?

  3. Open Issues cont • Path to consolidate IC and C-CDA • Which Common Information model to use? • FHIM • FHIR • CIMI • Figure out which is currently closest? • Solution architecture: • MDMI might be an excellent fit • At the end, recap the process in order to make recommendations to those doing this exercise for other domains • “bookends” approach – pick straightline case then outliers

  4. Open Issues 3 • V2 Referral msgs may be a V2 candidate for decision support • An issue with V2 msgs and decision support is that patient name etc is required but not needed for decision support; also, all decision support info ends up in OBX • Interest in looking at CCD • vMR is a possible common information model format

  5. CDS Follow-ups • Darrell to supply vMR cross-reference with field mappings • Clayton to investigate Arden/GELLO implementation of immunization decision support

More Related