Project Summary for Canonical Pedigree (Family History) Interoperability Implementation Guide
Visit Project Insight to see the full project details. *
Project Details
Number | 729 View Ballot Items List (with NIBs) |
---|---|
Name | Canonical Pedigree (Family History) Interoperability Implementation Guide |
Sponsor(s) | Clinical Genomics Work Group |
Co-Sponsor(s) | No Selection |
Steering Division | Clinical |
Description | The Canonical Pedigree Project (CPP) was proposed and approved at the HL7 Phoenix meeting of the Clinical Genomics work group in January, 2010. It is intended to improve adoption of the standard V3 pedigree message. It has three aspects: - Reference Pedigrees: Provide reference pedigree messages with corresponding text descriptions of the family history. Intended to be a resource for family history collection software verification. - Interoperability Testing: The internal storage of a pedigree is up to the host system. Furthermore, some interoperability standards want to represent a pedigree using alternate formats (e.g. CCD, vMR, clinical statements, etc.). The canonical pedigree project shall provide test guidance to verify that host systems and alternate formats are able to accurately maintain the relationships in the reference pedigrees. If full fidelity cannot be maintained, the guidance will help quantify the loss of fidelity. - Clinical Power: Many systems provide support only for simplified family histories. For example, they will capture that there were two instances of aunts with breast cancer. That simplified perspective is in contrast with one that maintains maternal vs. paternal line, the number of available aunts and clinical details such as age of onset. The intent behind this facet of CPP is to quantify the clinical benefits of improving the granularity of family and clinical histories. |
Project Facilitator | Scott Bolte |
Status | Archived |
SD Approval Date | Dec 22, 2010 |
TSC Approval Date | Jan 8, 2011 |
Type | Ballot - Informative |
Objectives / Deliverables | First draft of IG balloted for comment only - Target: 2011 Sep WGM Second draft of IG balloted as informational - Target: 2012 Jan WGM Final version of IG balloted as informational - Target: TBD Publishing of the Canonical Pedigree IG - Target: 2012 May WGM |
Next Milestone Date | 2013 May WGM |
Project End Date | 2013 May WGM |
Project Intent | Supplement to a Current Standard, Implementation Guide |
Project Need | The adoption of the HL7 Pedigree standard message is inhibited by a lack of interoperability testing. As of 2010, that has led to multiple systems that are generating incompatible messages. While wider use of the HL7 provided message schema would partially address that problem, there is still a problem verifying when messages are equivalent. This project focuses on the following interoperability needs. Well-Formed: An XML message is said to be well-formed if it conforms to the high-level XML syntax rules. Valid: An XML message is valid if it conforms to a schema definition that dictates the allowed content and ordering of elements. Equivalent: For interoperability, it is not sufficient that pedigree messages are valid. It is critical to be able to test if two pedigree messages are equivalent. |
Implementers | |
Security Risks | |
External Drivers | |
Common Names / Keywords/ Aliases | |
Lineage | |
Dependancies | |
Project Document Repository | http://wiki.hl7.org/index.php?title=Canonical_Pedigree_Project |
Backwards Compatibility | N/A |
External Vocabularies | |
Products | V3 Messages-Clinical |
Joint Copyright? | |
External Pjt Collaborators | Family history stakeholders who have expressed interest include Hughes Risk Apps, GE Healthcare, 5AM Solutions - implementation arm of the US Surgeon General's My Family Health Portrait, Intermountain Healthcare, and individual clinicians, to mention just a few. |
Realm | Realm Specific - Enter "U.S." or name of HL7 Affiliate below |
HL7 Affiliate | U.S. |
Stakeholders | N/A |
Vendors | EHR, PHR; Clinical Decision Support Systems; Lab |
Providers | Healthcare Institutions (hospitals, long term care, home care, mental health) |
Ballot Cycle Info | 2013 Jan Ballot Cycle Info: INFORMATIVE Ballot results: Met basic vote requirements. 3 Negatives to reconcile Document Name: HL7 Version 3 Implementation Guide: Family History/Pedigree Interoperability, Release 1 - US Realm Ballot Code: V3IG_CANONPED_R1_I1_2013JAN 2012 Sept Ballot Cycle Info: INFORMATIVE Ballot results: Postponed Document Name: HL7 Version 3 Implementation Guide: Family History/Pedigree Interoperability, Release 1 - US Realm Ballot Code: V3IG_CANONPED_R1_I1_2012SEP NIB Submitted By: Mollie Ullman-Cullere |
Misc Notes | June 2014: Per CG WG: This project has successfully completed resulting in the publication of an IG for Meaningful Use PMO archiving. March 2013: TSC approved the informative publication of HL7 Version 3 Implementation Guide: Implementation Guide: Family History/Pedigree Interoperability, Release 1 Sept 2011: M. Ullman-Cullere: We would like to suspend the following project. We have received feedback from ISO on the Pedigree model and want time to address before resuming work on the Canonical Pedigree Project. We would plan to resume in a year or so. PMO placed project On Hold. Ballot type notes: The intent is to provide guidance on the creation, comparison, transformation, and exchange of pedigree messages. In addition, the clinical impact of simplifying pedigrees may be documented. If in the course of that work deficiencies are found in the V3 standard, a revision to the standard may be made. The revision would be balloted as an independent project. |
U.S. Govt Interest? | |
USRSC Approval | |
FMG Approval | |
ARB Approval | |
Start Date | Oct 5, 2010 |
* A Project Insight User ID and password is required to access Project Insight. Contact the HL7 PMO at for more information.
Visit the Projects, Ballots and Standards Metrics Excel Report to view projects that are behind 120+ days along with other ballots and standards requiring a Work Group's attention.
Visit the Projects, Ballots and Standards Metrics Excel Report to view projects that are behind 120+ days along with other ballots and standards requiring a Work Group's attention.