Difference between revisions of "201901 EBMonFHIR"
BrianAlper (talk | contribs) (Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}") |
BrianAlper (talk | contribs) |
||
Line 3: | Line 3: | ||
__NOTOC__ | __NOTOC__ | ||
=Track Name= | =Track Name= | ||
+ | |||
+ | EBMonFHIR | ||
+ | |||
+ | [https://youtu.be/xQxyU_mzucI Evidence Based Medicine on FHIR Orientation Video] | ||
==Submitting WG/Project/Implementer Group== | ==Submitting WG/Project/Implementer Group== | ||
<!-- Who is asking for this track? --> | <!-- Who is asking for this track? --> | ||
+ | |||
+ | Clinical Decision Support WG | ||
==Justification== | ==Justification== | ||
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. --> | <!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. --> | ||
+ | |||
+ | This is the second connectathon of the EBMonFHIR project. Implementers need to work together to confirm ability to share the most basic element of "Summary of Findings" reports used heavily across systematic reviews and clinical practice guidelines. At the last Connectathon we created 4 resources (Evidence, EvidenceVariable, EffectEvidenceSynthesis, RiskEvidenceSynthesis) to meet this goal but found implementers not present found it confusing to implement. | ||
+ | |||
+ | We learned the need to make Profiles and perhaps an Implementation Guide and will focus the time on simpler implementations of the same basic use cases. | ||
+ | |||
+ | The EBMonFHIR project page can be found at http://wiki.hl7.org/index.php?title=EBMonFHIR | ||
+ | |||
+ | [https://docs.google.com/document/d/16j1dIUU4PmXqqOgamy44bxIPyO-WVTXQLaq0oy2PakA/ Introduction to EBMonFHIR] | ||
==Clinical input requested== | ==Clinical input requested== | ||
<!--Please indicate here if you would like input from the the Clinical community please indicate so here. The connectathon organizers will contact you to follow up. --> | <!--Please indicate here if you would like input from the the Clinical community please indicate so here. The connectathon organizers will contact you to follow up. --> | ||
+ | Not needed but clinicians may find the Evidence-Based Medicine concepts being developed of high interest and clinicians helped improve the model at the last connectathon. | ||
==Related tracks== | ==Related tracks== | ||
<!--Other tracks in this event that share similar goals and could either be combined, or an attendee could reasonable do both --> | <!--Other tracks in this event that share similar goals and could either be combined, or an attendee could reasonable do both --> | ||
+ | CDS Hooks and Clinical Reasoning tracks are likely to have overlap of interested parties but are not ready to be combined at this stage. | ||
==Proposed Track Lead== | ==Proposed Track Lead== | ||
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon --> | <!-- Name, email and Skype id of individual who will coordinate the track at the connectathon --> | ||
+ | Brian Alper | ||
+ | balper (at) ebsco.com | ||
+ | brian.alper | ||
+ | |||
See [[Connectathon_Track_Lead_Responsibilities]] | See [[Connectathon_Track_Lead_Responsibilities]] | ||
==Expected participants== | ==Expected participants== | ||
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track --> | <!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track --> | ||
+ | |||
+ | EBSCO Health | ||
+ | |||
+ | HarmonIQ | ||
+ | |||
+ | MedSide Healthcare | ||
+ | |||
+ | Qvera | ||
+ | |||
+ | potential participants from Europe - Cochrane, Duodecim, MAGIC, EvidencePrime | ||
==Roles== | ==Roles== | ||
Please include information here regarding how much advance preparation will be required if creating a client and/or server. | Please include information here regarding how much advance preparation will be required if creating a client and/or server. | ||
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on --> | <!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on --> | ||
− | === | + | |
+ | ===Evidence Reporter=== | ||
+ | <!-- Provide a description of the capabilities this role will have within the connectathon --> | ||
+ | Transmit a summary of findings from medical research. | ||
+ | ===Evidence Consumer=== | ||
<!-- Provide a description of the capabilities this role will have within the connectathon --> | <!-- Provide a description of the capabilities this role will have within the connectathon --> | ||
+ | Receive a summary of findings from medical research. | ||
==Scenarios== | ==Scenarios== |
Revision as of 12:16, 3 November 2018
Track Name
EBMonFHIR
Evidence Based Medicine on FHIR Orientation Video
Submitting WG/Project/Implementer Group
Clinical Decision Support WG
Justification
This is the second connectathon of the EBMonFHIR project. Implementers need to work together to confirm ability to share the most basic element of "Summary of Findings" reports used heavily across systematic reviews and clinical practice guidelines. At the last Connectathon we created 4 resources (Evidence, EvidenceVariable, EffectEvidenceSynthesis, RiskEvidenceSynthesis) to meet this goal but found implementers not present found it confusing to implement.
We learned the need to make Profiles and perhaps an Implementation Guide and will focus the time on simpler implementations of the same basic use cases.
The EBMonFHIR project page can be found at http://wiki.hl7.org/index.php?title=EBMonFHIR
Clinical input requested
Not needed but clinicians may find the Evidence-Based Medicine concepts being developed of high interest and clinicians helped improve the model at the last connectathon.
Related tracks
CDS Hooks and Clinical Reasoning tracks are likely to have overlap of interested parties but are not ready to be combined at this stage.
Proposed Track Lead
Brian Alper balper (at) ebsco.com brian.alper
See Connectathon_Track_Lead_Responsibilities
Expected participants
EBSCO Health
HarmonIQ
MedSide Healthcare
Qvera
potential participants from Europe - Cochrane, Duodecim, MAGIC, EvidencePrime
Roles
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
Evidence Reporter
Transmit a summary of findings from medical research.
Evidence Consumer
Receive a summary of findings from medical research.
Scenarios
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point: