Difference between revisions of "201809 Consumer Mediated Data Exchange (CMDE)"
(→Roles) |
|||
Line 31: | Line 31: | ||
==Roles== | ==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== | ==Scenarios== |
Revision as of 18:55, 2 August 2018
Consumer Mediated Data Exchange
Contents
Submitting WG/Project/Implementer Group
Justification
Related tracks
Proposed Track Lead
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: