This wiki has undergone a migration to Confluence found Here

Difference between revisions of "201809 Consumer Mediated Data Exchange (CMDE)"

From HL7Wiki
Jump to navigation Jump to search
Line 31: Line 31:
  
 
==Roles==
 
==Roles==
Please include information here regarding how much advance preparation will be required if creating a client and/or server.
+
Role 1 Name : Source of Record: Acts as intermediary
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on -->
+
 
===Role 1 Name===
+
Actor: HIE, EHR, immunization registries
<!-- Provide a description of the capabilities this role will have within the connectathon -->
+
 
 +
Stores
 +
 
 +
Role 2 : Electronic Consent Management System (eCMS)
 +
 
 +
Actor: Form filler FHIR SDC Questionnaire & QuestionnaireResponse, resource transformer, consent directive repository
 +
 
 +
Captures e-consent form and turns it into a computable consent directive
 +
 
 +
Role 3: IZ Client:  Immunization record viewer or client app
 +
 
 +
Actor:  EHR, patient portal, school documentation systems, personal health apps
 +
 
 +
Allows record to be viewed, managed and further distributed
 +
 
 +
Role 4: ACS/SLS: Access control system / security labeling service
 +
 
 +
Actor:  Rules Engine
 +
 
 +
Pulls consent directive to get policy, apply security label, and enforce filtering to the requested IZ resource
  
 
==Scenarios==
 
==Scenarios==

Revision as of 18:55, 2 August 2018

Consumer Mediated Data Exchange

Submitting WG/Project/Implementer Group

Andy Stechishin

Kathleen Connor

Aaron Seib

Justification

Related tracks

Proposed Track Lead

Andy Stechishin

Kathleen Connor

Aaron Seib

See Connectathon_Track_Lead_Responsibilities

Expected participants

Roles

Role 1 Name : Source of Record: Acts as intermediary

Actor: HIE, EHR, immunization registries

Stores

Role 2 : Electronic Consent Management System (eCMS)

Actor: Form filler FHIR SDC Questionnaire & QuestionnaireResponse, resource transformer, consent directive repository

Captures e-consent form and turns it into a computable consent directive

Role 3: IZ Client: Immunization record viewer or client app

Actor: EHR, patient portal, school documentation systems, personal health apps

Allows record to be viewed, managed and further distributed

Role 4: ACS/SLS: Access control system / security labeling service

Actor: Rules Engine

Pulls consent directive to get policy, apply security label, and enforce filtering to the requested IZ resource

Scenarios

Scenario Step 1 Name

Action:
Precondition:
Success Criteria:
Bonus point:


TestScript(s)

Security and Privacy Considerations