This wiki has undergone a migration to Confluence found Here
Difference between revisions of "Template for FHIR Connectathon Track Proposals"
Jump to navigation
Jump to search
m |
|||
| (22 intermediate revisions by 7 users not shown) | |||
| Line 1: | Line 1: | ||
<noinclude>[[Category:StyleGuides]]<big>To use this Template: | <noinclude>[[Category:StyleGuides]]<big>To use this Template: | ||
| − | #Search (or Go to) for a page with name like yyyymm_Track Name (with a proper year/month combination for the target connectathon) | + | #Search (or Go to) for a page with name like '''yyyymm_Track Name''' (with a proper year/month combination for the target connectathon) |
#Click on the '''RED''' link to the (previously) undefined page in order to edit it. | #Click on the '''RED''' link to the (previously) undefined page in order to edit it. | ||
#Type '''<nowiki>{{subst::Template for FHIR Connectathon Track Proposals}}</nowiki>''' as the '''only content''' for the new page. | #Type '''<nowiki>{{subst::Template for FHIR Connectathon Track Proposals}}</nowiki>''' as the '''only content''' for the new page. | ||
| Line 8: | Line 8: | ||
#Re-edit the page to fill in your proposal | #Re-edit the page to fill in your proposal | ||
#Save again | #Save again | ||
| + | |||
| + | |||
</big> | </big> | ||
</noinclude> | </noinclude> | ||
| − | [[Category: | + | [[Category:201901_FHIR_Connectathon_Track_Proposals|Jan2019 Proposals]] |
__NOTOC__ | __NOTOC__ | ||
=Track Name= | =Track Name= | ||
| Line 19: | Line 21: | ||
==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. --> | ||
| + | |||
| + | |||
| + | ==Clinical input requested== | ||
| + | <!--Please indicate here if you would like input from the the Clinical community please indicate so here. The connectathon organizers will contact you to follow up. --> | ||
| + | |||
| + | ==Related tracks== | ||
| + | <!--Other tracks in this event that share similar goals and could either be combined, or an attendee could reasonable do both --> | ||
==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]] | ||
==Expected participants== | ==Expected participants== | ||
| Line 27: | Line 37: | ||
==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=== | ===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== |
<!-- What will be the actions performed by participants? --> | <!-- What will be the actions performed by participants? --> | ||
| Line 43: | Line 54: | ||
==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] | ||
| + | --> | ||
| + | |||
| + | ==Security and Privacy Considerations== | ||
| + | <!-- Optional (for initial proposal): Address the topic of Privacy and Security. | ||
| + | * What Authentication/Authorization will be used (e.g. SMART on FHIR (OAuth), HEART (UMA/OAuth), IHE IUA (OAuth), generic OAuth, generic SAML, mutual-Auth-TLS), or explicitly indicate that it is out of scope and left to implementations. | ||
| + | * What Privacy Consent management will be used? When the Consent Resource is used, define how. | ||
| + | * What Audit Logging will be used? When the AuditEvent Resource is used, define expectations of what events will be logged and what each AuditEvent will contain. | ||
| + | * How will Provenance be used? Provenance use should be mandated when data is imported from other systems, so as to track that source of that data. Provenance should be used when data is authored by unusual sources, such as the Patient themselves or devices. | ||
| + | * How will security-labels be used? Security-labels are meta tags used to classify the data into various confidentiality, sensitivity, and integrity classifications. These security-labels are then available for use and available for access control decisions. | ||
| + | I am happy to help: JohnMoehrke@gmail.com -- security co-chair | ||
| + | --> | ||
Latest revision as of 17:37, 19 October 2018
To use this Template:
- Search (or Go to) for a page with name like yyyymm_Track Name (with a proper year/month combination for the target connectathon)
- Click on the RED link to the (previously) undefined page in order to edit it.
- Type {{subst::Template for FHIR Connectathon Track Proposals}} as the only content for the new page.
- Preview (if desired) to verify the reference was typed correctly
- "Save" the page.
- At this point, the contents of this template (with the exception of these instructions) will replace the substitution link.
- Re-edit the page to fill in your proposal
- Save again
Track Name
Submitting WG/Project/Implementer Group
Justification
Clinical input requested
Related tracks
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:
