This wiki has undergone a migration to Confluence found Here
Difference between revisions of "201809 EBMonFHIR"
Jump to navigation
Jump to search
BrianAlper (talk | contribs) |
BrianAlper (talk | contribs) |
||
| Line 13: | Line 13: | ||
==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 first connectathon of this new 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. | ||
==Proposed Track Lead== | ==Proposed Track Lead== | ||
Revision as of 19:01, 1 June 2018
Track Name
EBMonFHIR
Submitting WG/Project/Implementer Group
Clinical Decision Support WG
Justification
This is the first connectathon of this new 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.
Proposed Track Lead
See Connectathon_Track_Lead_Responsibilities
Expected participants
Roles
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
Role 1 Name
Scenarios
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
