| Rule type | Description |
|---|---|
| Based on declaration | Doctor with an active declaration can access all the patient's medical data. |
| Based on context episode | User can read medical data, that was collected during an episode of care, managed by the user's legal entity. |
| Based on diagnostic report | User can read medical data, that was collected as a part of a diagnostic report, managed by the user's legal entity. |
| Based on approval | User can read medical data, that was collected as a part of a diagnostic report or episode of care, that was allowed to read by a patients approval. |
| Based on origin episode | Doctor can read medical data, that was collected as a part of a diagnostic report or episode of care, created based on doctor's service request. Episode of care, that contains this service request, is considered as an origin episode in that case. |
Contexts ERD
| Rule | Rule type | Resource | Route | Initial context | Used contexts | Context source |
|---|---|---|---|---|---|---|
@rule_1 @read @episode @encounter @observation @condition @allergy_intolerance @immunization @risk_assessment @device @medication_statement @service_request @diagnostic_report Scenario: Doctor with active declaration can read all patient data Given Active declaration with patient And declaration from the same MSP When I require read access Then I can read | Based on declaration | episode | by id | patient | for all:{patient_id} form URL | |
by search params | ||||||
| encounter | by id | |||||
| by search params | ||||||
| in episode context by id | ||||||
| in episode context by search params | ||||||
| observation | by id | |||||
| by search params | ||||||
| in episode context by id | ||||||
| in episode context by search params | ||||||
| condition | by id | |||||
| by search params | ||||||
| in episode context by id | ||||||
| in episode context by search params | ||||||
| allergy_intolerance | by id | |||||
| by search params | ||||||
| in episode context by id | ||||||
| in episode context by search params | ||||||
| immunization | by id | |||||
| by search params | ||||||
| in episode context by id | ||||||
| in episode context by search params | ||||||
| risk_assessment | by id | |||||
| by search params | ||||||
| device | by id | |||||
| by search params | ||||||
| medication_statement | by id | |||||
| by search params | ||||||
| service_request | by id | |||||
| by search params | ||||||
| diagnostic_report | by id | |||||
| by search params | ||||||
| @rule_8 @read @observation @condition @allergy_intolerance @immunization @risk_assessment @device @medication_statement @diagnostic_report Scenario: Doctor can read all the data of encounter originated by episode, created in the doctors MSP Given Encounter context has been originated by mine episode When I require read access Then I can read | Based on origin episode | observation | by id | encounter | encounter.origin_episode.managing_organization | by id: selected from DB by search param: |
| by search param | ||||||
| condition | by id | |||||
| by search param | ||||||
| allergy_intolerance | ||||||
| by search param | ||||||
| immunization | ||||||
| by search param | ||||||
| risk_assessment | ||||||
| by search param | ||||||
| device | ||||||
| by search param | ||||||
| medication_statement | ||||||
| by search param | ||||||
| diagnostic_report | ||||||
| by search param |