Difference between revisions of "CSCR-098-CSCG-Incorporate Pedigree Family Structure"
Riksmithies (talk | contribs) |
Riksmithies (talk | contribs) |
||
| Line 23: | Line 23: | ||
This is how CS was at the time of the proposal: | This is how CS was at the time of the proposal: | ||
[[image:CSBeforeReorganisation.png|CS Before Reorganisation]] | [[image:CSBeforeReorganisation.png|CS Before Reorganisation]] | ||
| + | |||
| + | This is the actual structure that is needed, taken from POCG_RM000040UV.html (in Normative Edition, no longer in ballot) | ||
| + | |||
| + | [[image:GenomicsStructureWanted.jpg|Genomics Structure Wanted]] | ||
== Rationale == | == Rationale == | ||
Revision as of 11:02, 10 February 2012
Back to Clinical Statement Change Requests page.
| Submitted by: Hans Buitendijk | Revision date: May 13, 2009 |
| Submitted date: May 13, 2009 | Change request ID: CSCR-098 |
Issue
The Pedigree/Family History model is currently not derivable from the Clinical Statement making it challenging to more easily introduce Pedigree/Family History data wherever the SupportingClinicalStatement CMET is in play or where the Clinical Statement is the primary content model.
Recommendation
- Include the attached proposed model
- If there is an easier way to convey the same meaning and support the use case further described in Pedigree/Family History, the exact modeling attached does not need to be adhered to.
Feb-2012 - This was the original suggested new structure:
(
)
However since this was originally proposed, the CS model has been changed.
This is how CS was at the time of the proposal:
This is the actual structure that is needed, taken from POCG_RM000040UV.html (in Normative Edition, no longer in ballot)
Rationale
Discussion
Recommended Action Items
Resolution
4-Jun-2009 Motion to incorporate a Pedigree structure in CS and work through the modeling to get the best representation in CS. Charlie, Rik. Against: 0; Abstain: 1; In Favor: 3
