Revision as of 12:48, 9 June 2017

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

Please include information here regarding how much advance preparation will be required if creating a client and/or server.

Action:

Precondition:

Success Criteria:

Bonus point:

@@ Line 47: / Line 47: @@
 <!-- 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
 -->