This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Constrain time ranges in CDA R3"
Jump to navigation
Jump to search
(New page: {{CDA R3 Open Proposals}} Return to SDTC page; Return to CDA R3 Formal Proposals page. {|width=100% cellspacing=0 cellp...) |
|||
| Line 5: | Line 5: | ||
{|width=100% cellspacing=0 cellpadding=2 border=1 | {|width=100% cellspacing=0 cellpadding=2 border=1 | ||
| − | || '''Submitted by:''' Keith Boone | + | || '''Submitted by:''' Keith W. Boone ([[User:Kboone|Kboone]]) |
| − | || '''Revision date:''' | + | || '''Revision date:''' 20:42, 24 March 2009 (UTC) |
|- | |- | ||
| − | || '''Submitted date:''' | + | || '''Submitted date:''' 20:42, 24 March 2009 (UTC) |
|| '''Change request ID:''' <<Change Request ID>> | || '''Change request ID:''' <<Change Request ID>> | ||
|- | |- | ||
Revision as of 20:42, 24 March 2009
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
(Resolution is to be recorded here and in the referenced minutes, which are the authoritative source of resolution).
