This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Act in DEF Mood"
Jump to navigation
Jump to search
| Line 10: | Line 10: | ||
= Introduction = | = 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. | |
| − | |||
Revision as of 19:40, 17 July 2009
This page documents an Open MnM Hot Topic, i.e. a methodology issue requiring a resolution from Modeling and Methodology.
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.
