This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Proposal: add CareProvision(EVN) to Scheduling domain

From HL7Wiki
Revision as of 15:16, 9 March 2010 by Rene spronk (talk | contribs)
Jump to navigation Jump to search

Summary

  • This proposal seeks to add the A_CareEvent [identified] CMET to the Scheduling D-MIM and the response R-MIM to the Find Scheduled Encounters query. Oslo University Hospital have a use-case where they'd like to query for 'a scheduled encounter, which is part of an ongoing Careprovision'.

Storyboard

Storyboards require for the following details, all associated with the CareProvision:

  • It is unknown if the CareProvision (called: Care Period in the OUH specs) has an identifier. It is also unknown if the care provision has a type code.
  • The key things are: reason (diagnosis) for the care provision, responsible person, responsible unit (department, organizational part).

Proposal details

A CareProvision (see encounter part of the Patient Administration D-MIM) may be associated with (=have components) 0..* encounters. An encounter may be a component of 0..1 CareProvision events. Given that CareProvisions may have components in moods other than EVN (notably: INT), the appointment for the Encounter is part of the CareProvision just as much as the Encounter itself.

  • Add A_CareEvent [identified] with a COMPonentOf act relationship (cardinality: 0..1) to the ActAppointment class of the Scheduling D-MIM.
  • Extend the response model proposed by this (approved) Proposal: add Find Appointments Query with a "0..1 COMP A_CareEvent [identified] CMET" act relationship.