This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Keith Boone, 2007 constraints on condition"
Jump to navigation
Jump to search
| Line 4: | Line 4: | ||
1. condition.value is required, but if the only value you have is text, then this could be found in condition.text, and requiring condition.value gets in the way (especially if you want more compatibility with other HL7 standards, such as CDA Release 2). | 1. condition.value is required, but if the only value you have is text, then this could be found in condition.text, and requiring condition.value gets in the way (especially if you want more compatibility with other HL7 standards, such as CDA Release 2). | ||
| + | |||
2. condition.interpretationCode is also required, but in the above case, I find nothing in interpretationCode that SHOULD be required in the use case just provided. | 2. condition.interpretationCode is also required, but in the above case, I find nothing in interpretationCode that SHOULD be required in the use case just provided. | ||
Latest revision as of 17:54, 16 September 2008
Each care entry can have a "conditions" associated with it. One use for this is to describe the preconditions under which a substance administration is to occur (e.g. Tylenol 500mg, 1-2 tabs every four hours as needed for pain).
The issue I raise is that the constraints on condition are too restrictive:
1. condition.value is required, but if the only value you have is text, then this could be found in condition.text, and requiring condition.value gets in the way (especially if you want more compatibility with other HL7 standards, such as CDA Release 2).
2. condition.interpretationCode is also required, but in the above case, I find nothing in interpretationCode that SHOULD be required in the use case just provided.
