Difference between revisions of "Constrain time ranges in CDA R3"
Rene spronk (talk | contribs) m (Contrain time ranges in CDA R3 moved to Constrain time ranges in CDA R3: typo in title) |
|||
| Line 1: | Line 1: | ||
| − | {{CDA R3 | + | {{CDA R3 Closed Proposals}} |
Return to [[Structured Documents TC|SDTC]] page; Return to [[:category:CDA R3 Formal Proposals|CDA R3 Formal Proposals]] page. | Return to [[Structured Documents TC|SDTC]] page; Return to [[:category:CDA R3 Formal Proposals|CDA R3 Formal Proposals]] page. | ||
| Line 29: | Line 29: | ||
== Resolution == | == Resolution == | ||
| − | + | March 9, 2010: May conflict with our desire to map another committee's RMIM semantically. The rule is potentially something that should be stated in the RIM or Datatypes specification, such that it is applicable not only to CDA, but to all HL7 V3 models. abstain: 0; opposed: 0; in favor: 7. | |
Latest revision as of 21:43, 9 March 2010
Return to SDTC page; Return to CDA R3 Formal Proposals page.
| Submitted by: Keith W. Boone (Kboone) | Revision date: 20:42, 24 March 2009 (UTC) |
| Submitted date: 20:42, 24 March 2009 (UTC) | Change request ID: <<Change Request ID>> |
Issue
HL7 Data types allow for time ranges to be specified by any two of low, high, center and width. There are six different combinations here. I have found only two of the six to be necessary: low and high, or width alone when a time range is known, but not it's anchors.
Recommendation
Rationale
The rationale for constaining this is that it dramatically simplifies how the information is stored without any loss in what is conveyed.
Discussion
Recommended Action Items
Resolution
March 9, 2010: May conflict with our desire to map another committee's RMIM semantically. The rule is potentially something that should be stated in the RIM or Datatypes specification, such that it is applicable not only to CDA, but to all HL7 V3 models. abstain: 0; opposed: 0; in favor: 7.
