1 / 15

VMR Progress

VMR Progress. HL7 Baltimore October 2002. Points from May HL7. Need to distinguish Orders from Events Coping with Aggregate terms VMR as part of an API Alerts/triggers. With subclasses. R-MIM Changes: Order vs. Event. All Interventions now have three possible mood codes

taregan-martin
Télécharger la présentation

VMR Progress

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. VMR Progress HL7 Baltimore October 2002

  2. Points from May HL7 • Need to distinguish Orders from Events • Coping with Aggregate terms • VMR as part of an API • Alerts/triggers

  3. With subclasses

  4. R-MIM Changes: Order vs. Event • All Interventions now have three possible mood codes • INT – intent (for use in a plan) • ORD – order; not yet happened • EVN – event; record of it having happened

  5. Changes: Aggregates • Aggregate terms • E.g. Blood Pressure • Systolic • Diastolic • Observations can now be components of other observations. • Uses an act_relationship, type_cd COMP • OR we can do with Aggregate object • Discuss…

  6. Changes: Plans • Added • Relationship to Interventions • Relationship to Goals

  7. Changes: Intervention • Health Care intervention • Base class of all actions in UML diagram • Needed to specify services carried out for patients – e.g. ‘Annual Diabetic Review’ • This was in UML diagrams, but omitted from R-MIM in May

  8. Changes: Reasons • Reason for encounter • Reason for appointment • Reason for referral • -all of these are act_relationship to one of the choices

  9. API expression • VMR describes • classes used in an API • Attributes of the classes • Not the methods • API needs • Queries on real clinical system • Writes/updates on clinical system • Action requests to clinical system • Registration for trigger notification • Notification of events/triggers from clinical system

  10. DSS KB Has expressions using VMR terms CDSS module Queries Writes/updates Action requests Trigger requests Trigger events API - uses VMR objects/attributes/terms Terminology Mediation KB VMR <> host Clinical system adaptor Clinical System

  11. API parts • Queries, writes, updates • e.g. ‘haemoglobin values in past month’ • Return set of observations • Can be done as XML messages from R-MIM – use for loosely coupled systems • Can be done in OO IDL - useful for close coupled systems

  12. IDL definition of API

  13. Host System Services Carrying out action requests create a new action on host system record it as side effect

  14. Host System Services: Triggers

More Related