This wiki has undergone a migration to Confluence found Here

Difference between revisions of "Act in DEF Mood"

From HL7Wiki
Jump to navigation Jump to search
Line 10: Line 10:
 
= Introduction =
 
= Introduction =
  
In order to use static models for templates, we need to be able to have incomplete
+
Various challenges with using DEV (or EVN.CRT) mood have been identified. These are detailed here: http://wiki.hl7.org/images/d/d1/EMeasureMNMPresentation_17July2009.pdf
static models. An incomplete static model is a model that leaves some content open.
 
  
= Rationale =  
+
= Recommendations =
  
Usually a static model is complete - any content not described by the model is
+
[1] Document characteristic attributes: Current thinking is to assume that in EVN.CRT mood, no properties are documentation characteristic. Gunther suggests that we may need to split Act.statusCode into an Act.actStatusCode and an Act.recordStatusCode.
disallowed. For normal static models - D-MIMs, R-MIMs, CMETs - this makes
+
 
complete sense. But when it comes to templates, such completeness is often not
+
[2] Vocabulary binding: Current thinking is to include a local code, which in the local code system reflects a value set.
appropriate.
 

Revision as of 19:40, 17 July 2009

Introduction

Various challenges with using DEV (or EVN.CRT) mood have been identified. These are detailed here: http://wiki.hl7.org/images/d/d1/EMeasureMNMPresentation_17July2009.pdf

Recommendations

[1] Document characteristic attributes: Current thinking is to assume that in EVN.CRT mood, no properties are documentation characteristic. Gunther suggests that we may need to split Act.statusCode into an Act.actStatusCode and an Act.recordStatusCode.

[2] Vocabulary binding: Current thinking is to include a local code, which in the local code system reflects a value set.