View source for 201601 EHR Record Lifecycle Architecture


[[Category:201601_FHIR_Connectathon_Track_Proposals|Jan 2016 Proposals]]
__NOTOC__
=Track Name=

==Submitting WG/Project/Implementer Group==
HL7 EHR Work Group, Record Lifecycle Event Project Team
<!-- Who is asking for this track? -->

==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. -->

==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 -->

==Expected participants==
<!-- 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 are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
===Role 1 Name===
<!-- Provide a description of the capabilities this role will have within the connectathon -->

==Scenarios==
<!-- 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===
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 -->
:Precondition: <!-- What setup is required prior to executing this step? -->
:Success Criteria: <!-- How will the participants know if the test was successful? -->
:Bonus point: <!-- Any additional complexity to make the scenario more challenging -->

<!-- Provide a description of each task -->

==TestScript(s)==
<!-- Optional (for initial proposal): Provide links to the TestScript instance(s) that define the behavior to be tested.  
These should be committed to SVN under trunk/connectathons/[connectathon]
-->