Difference between revisions of "PicoElementDefinition FHIR Resource Proposal"
BrianAlper (talk | contribs) |
|||
| (17 intermediate revisions by 3 users not shown) | |||
| Line 7: | Line 7: | ||
</div> | </div> | ||
[[Category:FHIR Resource Proposal]] | [[Category:FHIR Resource Proposal]] | ||
| − | [[Category: | + | [[Category:Retracted FHIR Resource Proposal]] |
| Line 13: | Line 13: | ||
| − | = | + | =PicoElementDefinition= |
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
| Line 30: | Line 30: | ||
<!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | <!-- The name of the committee that is proposed to have responsibility for developing and maintaining the resources. --> | ||
| − | [[ | + | [[Clinical_Decision_Support]] |
==Committee Approval Date:== | ==Committee Approval Date:== | ||
| − | + | * Initial PSS: June 22, 2018 | |
| + | * CDS WG: September 12, 2018 | ||
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
<!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the resource (optional) --> | <!-- Additional work groups that may have an interest in contributing to, or reviewing the content of the resource (optional) --> | ||
| − | * | + | * Clinical Decision Support |
| − | * | + | * Clinical Quality Information |
| − | * | + | * Biomedical Research and Regulation |
==FHIR Resource Development Project Insight ID== | ==FHIR Resource Development Project Insight ID== | ||
<!-- Please specify the id of your work group’s PSS for doing FHIR work. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | <!-- Please specify the id of your work group’s PSS for doing FHIR work. (If submitted but not yet approved, just write “pending”.) The link to the PSS template can be found here: http://gforge.hl7.org/gf/download/docmanfileversion/6832/9398/HL7FHIR_DSTUballotPSS-20120529.doc --> | ||
| + | 1422 | ||
==Scope of coverage== | ==Scope of coverage== | ||
| Line 58: | Line 60: | ||
As a rule, resources should encompass all of these aspects. | As a rule, resources should encompass all of these aspects. | ||
--> | --> | ||
| + | The scope of the PicoElementDefintion resource is to describe a "PICO" element that knowledge (evidence, assertion, recommendation) is about. | ||
| + | PICO stands for: | ||
| + | * Population - the population within which exposures and outcomes are being considered | ||
| + | * Intervention - the conditional state or exposure state being described for which one is expressing the risk of or effect on an outcome | ||
| + | * Comparison - the alternative conditional state or alternative exposure state when one is comparing states for the effect on an outcome | ||
| + | * Outcome - the result or effect of an intervention or exposure in a population | ||
| + | |||
| + | PICO (and its variants like PECO or PICOT) is a universal acronym used in evidence-based medicine communities to clearly express research questions and evidence findings. | ||
| + | |||
| + | The PicoElementDefinition resource allows expression of the components of a PICO question in codeable and reusable formats. | ||
==RIM scope== | ==RIM scope== | ||
| Line 77: | Line 89: | ||
* Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | * Have the characteristics of high cohesion & low coupling – need to explore whether coupling is good some places, not elsewhere – layers from Bo’s document | ||
--> | --> | ||
| + | Across the evidence-based medicine community (hundreds of thousands of people communicating the results of healthcare research and recommendations), the PICO elements are the foundational components of expressing what evidence assertions and recommendations are about. Standardizing the specification of these PICO element definitions is necessary to support interoperability across the evidence-based medicine domain. | ||
==Expected implementations== | ==Expected implementations== | ||
<!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | <!--Key resources are justified by CCDA, for resources not deemed "key", what interest is there by implementers in using this particular resource. Provide named implementations if possible - ideally provide multiple independent implementations. --> | ||
| + | Many knowledge producers who express the biomedical research community knowledge will be the implementers using this resources. Examples of these knowledge producers include Agency for Healthcare Research and Quality (AHRQ), Centers for Disease Control and Prevention (CDC), Cochrane, Duodecim Medical Publications Ltd (from the Finnish Medical Society), EBSCO Health, MAGIC (stands for Making GRADE the Irresistible Choice), and numerous guideline development organizations. | ||
==Content sources== | ==Content sources== | ||
| Line 87: | Line 101: | ||
Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? --> | Are there any source specifications that you wish to consult but are concerned about access to or expertise to consider? --> | ||
| + | |||
| + | None expected beyond the standard source specifications | ||
==Example Scenarios== | ==Example Scenarios== | ||
<!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | <!-- Provide a listing of the types of scenarios to be represented in the examples produced for this resource. They should demonstrate the full scope of the resource and allow exercising of the resources capabilities (full element coverage, inclusion & omission of optional elements, repeating and singleton repeating elements, etc.) --> | ||
| + | |||
| + | Description of the population for which a recommendation or evidence summary is applicable | ||
| + | Description of the intervention or exposure for which a recommendation or evidence summary is applicable | ||
| + | Description of the outcome that an evidence summary is about | ||
| + | |||
| + | These descriptions could be used in coded specifications of recommendations from clinical practice guidelines to facilitate the translation from guidelines to clinical decision support artifacts. | ||
| + | |||
| + | These descriptions could be used in Summary of Findings tables from systematic reviews to facilitate the representation of medical knowledge when creating recommendations. | ||
| + | |||
| + | These descriptions could be used in classification of new evidence reports to facilitate recognition of signal for updating existing evidence summaries and recommendations. | ||
==Resource Relationships== | ==Resource Relationships== | ||
| Line 102: | Line 128: | ||
Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | Reference to resources is really only relevant at the "same or higher level" (Bo – fix this wording) | ||
--> | --> | ||
| + | |||
| + | This resource does not reference other resources as it is the "atomic" level. | ||
| + | |||
| + | Multiple resources describing evidence findings (EffectEvidenceSynthesis, EffectEvidenceBit, RiskEvidenceSynthesis, RiskEvidenceBit) will reference PicoElementDefinition to describe what the evidence findings are about. | ||
| + | |||
| + | Recommendation resources will reference 3 PicoElementDefinition resources to describe the population for whom the recommendation is intended, the exposure being recommended and the exposureAlternative being recommended against. This common pattern will be defined as a PicDefinition resource to bundle the three PicoElementDefinition resources for unique identification and searching. | ||
==Resource Boundaries== | ==Resource Boundaries== | ||
| Line 108: | Line 140: | ||
Are we confident existing implementations will be able to make the distinction? --> | Are we confident existing implementations will be able to make the distinction? --> | ||
| + | |||
| + | To be determined if implementers have questions that need explanations to support distinction and clarification | ||
==Timelines== | ==Timelines== | ||
<!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | <!-- Indicate the target date for having the resource complete from a committee perspective and ready for vetting and voting --> | ||
| + | |||
| + | First STU Ballot 2019 May | ||
==gForge Users== | ==gForge Users== | ||
<!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | <!-- Identify the userids who will require commit access to gForge to maintain the resource. (Ensure all users have registered for gForge.) --> | ||
| + | |||
| + | brynrhodes (github user) | ||
| + | KhalidShahin-EBSCO (github user) | ||
==When Resource Proposal Is Complete== | ==When Resource Proposal Is Complete== | ||
Latest revision as of 20:44, 26 September 2018
This page documents a Pending FHIR Resource Proposal
Contents
- 1 PicoElementDefinition
- 1.1 Owning work group name
- 1.2 Committee Approval Date:
- 1.3 Contributing or Reviewing Work Groups
- 1.4 FHIR Resource Development Project Insight ID
- 1.5 Scope of coverage
- 1.6 RIM scope
- 1.7 Resource appropriateness
- 1.8 Expected implementations
- 1.9 Content sources
- 1.10 Example Scenarios
- 1.11 Resource Relationships
- 1.12 Resource Boundaries
- 1.13 Timelines
- 1.14 gForge Users
- 1.15 When Resource Proposal Is Complete
- 1.16 FMG Notes
PicoElementDefinition
Owning work group name
Committee Approval Date:
- Initial PSS: June 22, 2018
- CDS WG: September 12, 2018
Contributing or Reviewing Work Groups
- Clinical Decision Support
- Clinical Quality Information
- Biomedical Research and Regulation
FHIR Resource Development Project Insight ID
1422
Scope of coverage
The scope of the PicoElementDefintion resource is to describe a "PICO" element that knowledge (evidence, assertion, recommendation) is about. PICO stands for:
- Population - the population within which exposures and outcomes are being considered
- Intervention - the conditional state or exposure state being described for which one is expressing the risk of or effect on an outcome
- Comparison - the alternative conditional state or alternative exposure state when one is comparing states for the effect on an outcome
- Outcome - the result or effect of an intervention or exposure in a population
PICO (and its variants like PECO or PICOT) is a universal acronym used in evidence-based medicine communities to clearly express research questions and evidence findings.
The PicoElementDefinition resource allows expression of the components of a PICO question in codeable and reusable formats.
RIM scope
Resource appropriateness
Across the evidence-based medicine community (hundreds of thousands of people communicating the results of healthcare research and recommendations), the PICO elements are the foundational components of expressing what evidence assertions and recommendations are about. Standardizing the specification of these PICO element definitions is necessary to support interoperability across the evidence-based medicine domain.
Expected implementations
Many knowledge producers who express the biomedical research community knowledge will be the implementers using this resources. Examples of these knowledge producers include Agency for Healthcare Research and Quality (AHRQ), Centers for Disease Control and Prevention (CDC), Cochrane, Duodecim Medical Publications Ltd (from the Finnish Medical Society), EBSCO Health, MAGIC (stands for Making GRADE the Irresistible Choice), and numerous guideline development organizations.
Content sources
None expected beyond the standard source specifications
Example Scenarios
Description of the population for which a recommendation or evidence summary is applicable Description of the intervention or exposure for which a recommendation or evidence summary is applicable Description of the outcome that an evidence summary is about
These descriptions could be used in coded specifications of recommendations from clinical practice guidelines to facilitate the translation from guidelines to clinical decision support artifacts.
These descriptions could be used in Summary of Findings tables from systematic reviews to facilitate the representation of medical knowledge when creating recommendations.
These descriptions could be used in classification of new evidence reports to facilitate recognition of signal for updating existing evidence summaries and recommendations.
Resource Relationships
This resource does not reference other resources as it is the "atomic" level.
Multiple resources describing evidence findings (EffectEvidenceSynthesis, EffectEvidenceBit, RiskEvidenceSynthesis, RiskEvidenceBit) will reference PicoElementDefinition to describe what the evidence findings are about.
Recommendation resources will reference 3 PicoElementDefinition resources to describe the population for whom the recommendation is intended, the exposure being recommended and the exposureAlternative being recommended against. This common pattern will be defined as a PicDefinition resource to bundle the three PicoElementDefinition resources for unique identification and searching.
Resource Boundaries
To be determined if implementers have questions that need explanations to support distinction and clarification
Timelines
First STU Ballot 2019 May
gForge Users
brynrhodes (github user) KhalidShahin-EBSCO (github user)
When Resource Proposal Is Complete
When you have completed your proposal, please send an email to FMGcontact@HL7.org
