This wiki has undergone a migration to Confluence found Here
<meta name="googlebot" content="noindex">

Difference between revisions of "201601 CDS Hooks Connectathon Track Proposal"

From HL7Wiki
Jump to navigation Jump to search
(This proposal has been merged into 201601_CDS_on_FHIR_Connectathon_Track_Proposal)
 
(7 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
[[Category:201601_FHIR_Connectathon_Track_Proposals|Jan 2016 Proposals]]
 
[[Category:201601_FHIR_Connectathon_Track_Proposals|Jan 2016 Proposals]]
 
__NOTOC__
 
__NOTOC__
=Track Name=
+
=CDS Hooks=
  
==Submitting WG/Project/Implementer Group==
+
This proposal has been merged into [[201601_CDS_on_FHIR_Connectathon_Track_Proposal]].
<!-- Who is asking for this track? -->
 
 
 
==Justification==
 
<!--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==
 
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon -->
 
 
 
 
 
* Kevin Shekleton
 
** Email: kevin dot shekleton at cerner dot com
 
** Skype: kevin.shekleton
 
 
 
==Expected participants==
 
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track -->
 
 
 
* Cerner (Kevin Shekleton)
 
* SMART Health IT (Josh Mandel)
 
 
 
==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? -->
 
 
 
===Scenario Step 1 Name===
 
: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]
 
-->
 

Latest revision as of 13:21, 23 November 2015


CDS Hooks

This proposal has been merged into 201601_CDS_on_FHIR_Connectathon_Track_Proposal.