Difference between revisions of "PicDefinition FHIR Resource Proposal"
BrianAlper (talk | contribs) |
|||
| (10 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: | ||
| − | = | + | =PicDefinition= |
<!-- Resource names should meet the following characteristics: | <!-- Resource names should meet the following characteristics: | ||
| Line 33: | Line 33: | ||
==Committee Approval Date:== | ==Committee Approval Date:== | ||
| − | June 22, 2018 | + | * Initial PSS: June 22, 2018 |
| + | * CDS WG: September 12, 2018 | ||
==Contributing or Reviewing Work Groups== | ==Contributing or Reviewing Work Groups== | ||
| Line 59: | 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 | + | The scope of the PicDefinition resource is to describe the conditional state (population and exposures being compared within a population) that knowledge (evidence, assertion, recommendation) is about. |
The PIC is a commonly bundled triad from the "PICO" specification of medical knowledge: | The PIC is a commonly bundled triad from the "PICO" specification of medical knowledge: | ||
| Line 70: | Line 71: | ||
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. | 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 | + | The PicDefinition resource allows expression of the higher-order concept for recommendations in healthcare where multiple outcomes are considered. |
==RIM scope== | ==RIM scope== | ||
| Line 96: | Line 97: | ||
<!--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 102: | Line 105: | ||
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, and Description of the comparator state or the evidence is about or what the recommendation is against. | ||
| + | |||
| + | These descriptions could be used in coded specifications of recommendations from clinical practice guidelines to facilitate searching for recommendations that match an individual patient (eg patient is in the population and meets the criteria for the comparator state but not the criteria for the recommended exposure state) | ||
| + | |||
| + | 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 117: | Line 130: | ||
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) | ||
--> | --> | ||
| + | |||
| + | The PicDefinition resource reference the PicoElementDefinition resource three times to clearly specify the triad relationship. | ||
| + | |||
| + | Multiple resources describing evidence findings (EffectEvidenceSynthesis, EffectEvidenceBit) may reference PicDefinition rather than 3 separate PicoElementDefinition references to describe what the evidence findings are about. | ||
| + | |||
| + | Recommendation resources will reference the PicDefinition resource to describe the population for whom the recommendation is intended, the exposure being recommended and the exposureAlternative being recommended against. | ||
| + | |||
| + | The PicDefintion resource bundles a very common pattern and specification of 3 PicoElementDefinition resources with their relationships and will be used for unique identification and searching. | ||
==Resource Boundaries== | ==Resource Boundaries== | ||
| Line 123: | Line 144: | ||
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. | ||
| + | |||
| + | A Recommendation resource may include strength of recommendation, certainty, and justification concepts. The PicDefinition resource would not include these concepts. | ||
==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 PicDefinition
- 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
PicDefinition
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 PicDefinition resource is to describe the conditional state (population and exposures being compared within a population) that knowledge (evidence, assertion, recommendation) is about.
The PIC is a commonly bundled triad from the "PICO" specification of medical knowledge:
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 PicDefinition resource allows expression of the higher-order concept for recommendations in healthcare where multiple outcomes are considered.
RIM scope
Resource appropriateness
Across the evidence-based medicine community (hundreds of thousands of people communicating the results of healthcare research and recommendations), the PIC specification is the primary method for expressing what evidence assertions and recommendations are about. Standardizing the PIC specification 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, and Description of the comparator state or the evidence is about or what the recommendation is against.
These descriptions could be used in coded specifications of recommendations from clinical practice guidelines to facilitate searching for recommendations that match an individual patient (eg patient is in the population and meets the criteria for the comparator state but not the criteria for the recommended exposure state)
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
The PicDefinition resource reference the PicoElementDefinition resource three times to clearly specify the triad relationship.
Multiple resources describing evidence findings (EffectEvidenceSynthesis, EffectEvidenceBit) may reference PicDefinition rather than 3 separate PicoElementDefinition references to describe what the evidence findings are about.
Recommendation resources will reference the PicDefinition resource to describe the population for whom the recommendation is intended, the exposure being recommended and the exposureAlternative being recommended against.
The PicDefintion resource bundles a very common pattern and specification of 3 PicoElementDefinition resources with their relationships and will be used for unique identification and searching.
Resource Boundaries
To be determined if implementers have questions that need explanations to support distinction and clarification.
A Recommendation resource may include strength of recommendation, certainty, and justification concepts. The PicDefinition resource would not include these concepts.
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
