This wiki has undergone a migration to Confluence found Here
Difference between revisions of "201609 Patient Track Proposal"
Jump to navigation
Jump to search
(FHIR Connectathon 13 September 2016 Patient Track Proposal) |
(Re-initialize page) |
||
Line 1: | Line 1: | ||
− | + | ||
− | [[Category:201609_FHIR_Connectathon_Track_Proposals| | + | [[Category:201609_FHIR_Connectathon_Track_Proposals|May 2016 Proposals]] |
__NOTOC__ | __NOTOC__ | ||
− | = | + | =Track Name= |
− | |||
− | |||
− | |||
− | |||
− | |||
==Submitting WG/Project/Implementer Group== | ==Submitting WG/Project/Implementer Group== | ||
− | + | <!-- Who is asking for this track? --> | |
==Justification== | ==Justification== | ||
<!--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== | ||
<!-- 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 --> | ||
− | |||
− | |||
See [[Connectathon_Track_Lead_Responsibilities]] | See [[Connectathon_Track_Lead_Responsibilities]] | ||
==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 --> | ||
− | |||
==Roles== | ==Roles== | ||
+ | Please include information here regarding how much advance preparation will be required if creating a client and/or server. | ||
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on --> | <!-- 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 --> | <!-- Provide a description of the capabilities this role will have within the connectathon --> | ||
− | |||
− | |||
− | |||
− | |||
− | |||
==Scenarios== | ==Scenarios== | ||
<!-- What will be the actions performed by participants? --> | <!-- 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)== | ==TestScript(s)== | ||
− | <!-- Optional (for initial proposal): Provide links to the TestScript instance(s) that define the behavior to be tested | + | <!-- 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] | |
− | + | --> |
Revision as of 19:42, 5 June 2016
Track Name
Submitting WG/Project/Implementer Group
Justification
Proposed Track Lead
See Connectathon_Track_Lead_Responsibilities
Expected participants
Roles
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
Role 1 Name
Scenarios
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point: