This wiki has undergone a migration to Confluence found Here
Difference between revisions of "DiagnosticReportGenetics FHIR Profile Proposal"
Jump to navigation
Jump to search
(Created page with "{{subst::Template:FHIR Profile Proposal}}") |
|||
| Line 14: | Line 14: | ||
| − | = | + | =DiagnosticReportGenetics= |
| − | + | The DiagnosticReportGenetics profile extends the DiagnosticReport resource to enable reporting of structured genetic test results by referring to the ObservationGenetics profile. In addition, the genetics profile denotes condition context for genetic testing, which may influence reported variants and interpretation for large genomic testing panels and provides references to the FamilyMemberHistory resource, the Condition resource. | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
==Profile balloting plans== | ==Profile balloting plans== | ||
| + | STU3 | ||
==Profile Details== | ==Profile Details== | ||
| + | |||
| + | The DiagnosticReportGenetics profile supports reporting of DNA variants at the genomic, cDNA, and protein change level. In addition, a condition context may be provided, as AssessedCondition. For large genomic tests, a condition may be used as an input into the analytic pipeline to aid in the identification of clinically relevant variants related to the test order. | ||
===Profiled Resource(s)=== | ===Profiled Resource(s)=== | ||
| − | + | * [http://hl7-fhir.github.io/diagnosticreport.html DiagnosticReport] | |
| − | |||
====Constraints to be Applied==== | ====Constraints to be Applied==== | ||
| − | + | The following constraints are applied to the DiagnosticReport resource as necessary: | |
| − | * | + | * Constrain the cardinality of the data elements within the resource. |
| − | * | + | * Constrain the mustSupport attribute of the data elements within the resource. |
| + | * Define searchParameters as necessary for the resource. | ||
| + | * Constrain vocabularies for the resources as applicable. | ||
====Extensions to be Applied==== | ====Extensions to be Applied==== | ||
| − | + | The following extensions are applied to the DiagnosticReport resource as appropriate: | |
| − | * | + | * Clinical genomics specific extensions. |
| − | |||
===Example Scenarios=== | ===Example Scenarios=== | ||
| − | + | * Query Examples for DiagnosticReport resource. | |
| + | * Query Result Examples for DiagnosticReport resource. | ||
===Scope of coverage=== | ===Scope of coverage=== | ||
| − | + | * Subject: patient | |
| − | + | * Disciplines: Patient Care, Clinical Research, Public Health | |
| − | + | * Delivery Environment: Inpatient, Ambulatory, Community, Emergency, etc. | |
| − | * Subject: | ||
| − | * Disciplines: | ||
| − | * Delivery | ||
| − | |||
| − | |||
| − | |||
| − | |||
===Realm=== | ===Realm=== | ||
| − | + | Clinical genomics. | |
==Ownership== | ==Ownership== | ||
===Owning committee name=== | ===Owning committee name=== | ||
| − | + | [[Clinical Genomics]] | |
| − | [[ | ||
===Contributing or Reviewing Work Groups=== | ===Contributing or Reviewing Work Groups=== | ||
| − | + | * None | |
| − | * | ||
| − | |||
| − | |||
===Expected implementations=== | ===Expected implementations=== | ||
| Line 90: | Line 72: | ||
===gForge Users=== | ===gForge Users=== | ||
| − | + | * Gil Alterovitz | |
| − | + | * Gaston Fiore | |
===FHIR Profile Development Project Insight ID=== | ===FHIR Profile Development Project Insight ID=== | ||
| − | + | 1110 | |
==Plans== | ==Plans== | ||
===Timelines=== | ===Timelines=== | ||
| − | + | *July 2016 | |
| − | * | ||
===Balloting Requirements=== | ===Balloting Requirements=== | ||
| − | |||
| − | |||
| − | |||
*Ballot with next FHIR DSTU or Normative Edition | *Ballot with next FHIR DSTU or Normative Edition | ||
| − | |||
| − | |||
| − | |||
| − | |||
Desired Ballot Date | Desired Ballot Date | ||
| − | * | + | *End 2016 |
Revision as of 12:20, 24 May 2016
This page documents a Pending FHIR Resource Proposal
Contents
DiagnosticReportGenetics
The DiagnosticReportGenetics profile extends the DiagnosticReport resource to enable reporting of structured genetic test results by referring to the ObservationGenetics profile. In addition, the genetics profile denotes condition context for genetic testing, which may influence reported variants and interpretation for large genomic testing panels and provides references to the FamilyMemberHistory resource, the Condition resource.
Profile balloting plans
STU3
Profile Details
The DiagnosticReportGenetics profile supports reporting of DNA variants at the genomic, cDNA, and protein change level. In addition, a condition context may be provided, as AssessedCondition. For large genomic tests, a condition may be used as an input into the analytic pipeline to aid in the identification of clinically relevant variants related to the test order.
Profiled Resource(s)
Constraints to be Applied
The following constraints are applied to the DiagnosticReport resource as necessary:
- Constrain the cardinality of the data elements within the resource.
- Constrain the mustSupport attribute of the data elements within the resource.
- Define searchParameters as necessary for the resource.
- Constrain vocabularies for the resources as applicable.
Extensions to be Applied
The following extensions are applied to the DiagnosticReport resource as appropriate:
- Clinical genomics specific extensions.
Example Scenarios
- Query Examples for DiagnosticReport resource.
- Query Result Examples for DiagnosticReport resource.
Scope of coverage
- Subject: patient
- Disciplines: Patient Care, Clinical Research, Public Health
- Delivery Environment: Inpatient, Ambulatory, Community, Emergency, etc.
Realm
Clinical genomics.
Ownership
Owning committee name
Contributing or Reviewing Work Groups
- None
Expected implementations
gForge Users
- Gil Alterovitz
- Gaston Fiore
FHIR Profile Development Project Insight ID
1110
Plans
Timelines
- July 2016
Balloting Requirements
- Ballot with next FHIR DSTU or Normative Edition
Desired Ballot Date
- End 2016
