Difference between revisions of "201601 EHR Record Lifecycle Architecture"
Gdickinson (talk | contribs) (Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}") |
Gdickinson (talk | contribs) |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
==Submitting WG/Project/Implementer Group== | ==Submitting WG/Project/Implementer Group== | ||
| + | HL7 EHR Work Group, Record Lifecycle Event Project Team | ||
<!-- Who is asking for this track? --> | <!-- Who is asking for this track? --> | ||
==Justification== | ==Justification== | ||
| + | > Implements Implementer's Safety Check List, Item 9, regarding best practice for creating, reading and/or updating FHIR resource instances with corresponding AuditEvent and Provenance instances: http://hl7.org/fhir/implementation.html | ||
| + | |||
| + | > 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 | ||
| + | |||
| + | Knapp Consulting, Inc. | ||
==Roles== | ==Roles== | ||
| Line 23: | Line 37: | ||
==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=== | ||
| + | See Connectathon 10 Track 4 for details: http://wiki.hl7.org/index.php?title=FHIR_Connectathon_10 | ||
| + | |||
:Action: <!--Who does what? (Use the role names listed above when referring to the participants --> | :Action: <!--Who does what? (Use the role names listed above when referring to the participants --> | ||
:Precondition: <!-- What setup is required prior to executing this step? --> | :Precondition: <!-- What setup is required prior to executing this step? --> | ||
Latest revision as of 23:14, 29 November 2015
Track Name
Submitting WG/Project/Implementer Group
HL7 EHR Work Group, Record Lifecycle Event Project Team
Justification
> Implements Implementer's Safety Check List, Item 9, regarding best practice for creating, reading and/or updating FHIR resource instances with corresponding AuditEvent and Provenance instances: http://hl7.org/fhir/implementation.html
> 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:
