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

Difference between revisions of "Proposal: add CareProvision(EVN) to Scheduling domain"

From HL7Wiki
Jump to navigation Jump to search
(New page: ==Summary== *This proposal seeks to add the A_CareProvision [identified] CMET to the Scheduling D-MIM and the response R-MIM to the Find Scheduled Encounters query. Oslo University Hospita...)
 
Line 1: Line 1:
 
==Summary==
 
==Summary==
*This proposal seeks to add the A_CareProvision [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 'schedule and encounter, which is part of an ongoing Careprovision'.
+
*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==
 
==Storyboard==
 +
 +
 +
==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.

Revision as of 13:02, 9 March 2010

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

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.