Difference between revisions of "201601 EHR Record Lifecycle Architecture"
Gdickinson (talk | contribs) |
Gdickinson (talk | contribs) |
||
| Line 20: | Line 20: | ||
<!-- 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 | US Veterans Administration | ||
| + | Knapp Consulting, Inc. | ||
==Roles== | ==Roles== | ||
Revision as of 22:52, 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 Knapp Consulting, Inc.
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
See Connectathon 10 Track 4 for details: http://wiki.hl7.org/index.php?title=FHIR_Connectathon_10
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
