This wiki has undergone a migration to Confluence found Here
Difference between revisions of "CSCR-084-PHER-Add Uncertainty Code"
Jump to navigation
Jump to search
(New page: Back to Clinical Statement Change Requests page. {|width=100% cellspacing=0 cellpadding=2 border=1 || '''Submitted by:''' Austin Kreisler || '''Revision date:''' 11/24/2008 |- || '''Su...) |
Hbuitendijk (talk | contribs) |
||
Line 27: | Line 27: | ||
== Resolution == | == Resolution == | ||
+ | Motion to accept. Austin Kreisler, Patrick Loyd | ||
+ | <BR> | ||
+ | There is no degree to the level of certainty (certain, uncertain, no assertion of certainty). | ||
+ | <BR> | ||
+ | Against: 0; Abstain: 0; In Favor: 6 |
Revision as of 21:44, 29 January 2009
Back to Clinical Statement Change Requests page.
Submitted by: Austin Kreisler | Revision date: 11/24/2008 |
Submitted date: 11/24/2008 | Change request ID: CSCR-084 |
Issue
Sometimes in public health reporting the relationship between two acts is unclear.
Recommendation
- Add the uncertaintyCode attribute to the sourceOf2/targetOf and sourceOf1 act relationships in the CS model.
Rationale
In one model for documenting exposures the relationship between an acquisition exposure event and a transmission exposure event may be uncertain.
Discussion
Recommended Action Items
Add the following attribute to the sourceOf2/targetOf and sourceOf1 act relationships:
- uncertaintyCode – CE CNE [0..1] <= ActUncertainty (optional)
- (RIM) A code indicating whether the specific relationship between the source and target Acts has been asserted to be uncertain in any way.
Resolution
Motion to accept. Austin Kreisler, Patrick Loyd
There is no degree to the level of certainty (certain, uncertain, no assertion of certainty).
Against: 0; Abstain: 0; In Favor: 6