Difference between revisions of "201601 EHR Record Lifecycle Architecture"
Gdickinson (talk | contribs) |
Gdickinson (talk | contribs) |
||
| Line 9: | Line 9: | ||
==Justification== | ==Justification== | ||
| + | Piggybacks on other Connectathon tracks. Based on Record Lifecycle Event Implementation Guide - part of FHIR DSTU-2: http://hl7.org/fhir/ehrsrle/ehrsrle.html. Requires AuditEvent when resources are Create(d), Read or Update(d). Requires Provenance when resources are Create(d) or Update(d). | ||
<!--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. --> | ||
==Proposed Track Lead== | ==Proposed Track Lead== | ||
| + | Gary Dickinson, CentriHealth, gary.dickinson@ehr-standards.com | ||
| + | Kathleen Connor, kathleen_connor@comcast.net | ||
<!-- 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 --> | ||
==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 --> | ||
| + | US Veterans Administration | ||
==Roles== | ==Roles== | ||
| Line 24: | Line 28: | ||
==Scenarios== | ==Scenarios== | ||
<!-- What will be the actions performed by participants? --> | <!-- What will be the actions performed by participants? --> | ||
| + | Scenarios are defined within each Connectathon track. This track has no scenarios of its own, instead piggybacks on the other tracks where FHIR resource instances are Create(d), Read and/or Update(d). See Justification above. | ||
===Scenario Step 1 Name=== | ===Scenario Step 1 Name=== | ||
| Line 30: | Line 35: | ||
:Success Criteria: <!-- How will the participants know if the test was successful? --> | :Success Criteria: <!-- How will the participants know if the test was successful? --> | ||
:Bonus point: <!-- Any additional complexity to make the scenario more challenging --> | :Bonus point: <!-- Any additional complexity to make the scenario more challenging --> | ||
| + | |||
| + | See Connectathon 10 Track 4 for details: http://wiki.hl7.org/index.php?title=FHIR_Connectathon_10 | ||
<!-- Provide a description of each task --> | <!-- Provide a description of each task --> | ||
Revision as of 22:48, 29 November 2015
Track Name
Submitting WG/Project/Implementer Group
HL7 EHR Work Group, Record Lifecycle Event Project Team
Justification
Piggybacks on other Connectathon tracks. Based on Record Lifecycle Event Implementation Guide - part of FHIR DSTU-2: http://hl7.org/fhir/ehrsrle/ehrsrle.html. Requires AuditEvent when resources are Create(d), Read or Update(d). Requires Provenance when resources are Create(d) or Update(d).
Proposed Track Lead
Gary Dickinson, CentriHealth, gary.dickinson@ehr-standards.com Kathleen Connor, kathleen_connor@comcast.net
Expected participants
US Veterans Administration
Roles
Role 1 Name
Scenarios
Scenarios are defined within each Connectathon track. This track has no scenarios of its own, instead piggybacks on the other tracks where FHIR resource instances are Create(d), Read and/or Update(d). See Justification above.
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
See Connectathon 10 Track 4 for details: http://wiki.hl7.org/index.php?title=FHIR_Connectathon_10
