ЕСОЗ - публічна документація

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Rule typeDescription
Based on declarationDoctor with an active declaration can access all the patient's medical data.
Based on context episodeUser can read medical data, that was collected during an episode of care, managed by the user's legal entity.  
Based on diagnostic reportUser can read medical data, that was collected as a part of a diagnostic report, managed by the user's legal entity.
Based on approvalUser 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 episodeDoctor 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



RuleRule typeResourceRouteInitial contextImplementationContext 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 declarationepisodeby idpatient











for all:{patient_id} form URL







by search params

encounterby id
by search params
in episode context by id
in episode context by search params
observationby id
by search params
in episode context by id
in episode context by search params
conditionby id
by search params
in episode context by id
in episode context by search params
allergy_intoleranceby id
by search params
in episode context by id
in episode context by search params
immunizationby id
by search params
in episode context by id
in episode context by search params
risk_assessmentby id
by search params
deviceby id
by search params
medication_statementby id
by search params
service_requestby id
by search params
diagnostic_reportby id
by search params

@rule_5

@read @episode @encounter @observation @condition @allergy_intolerance @immunization @risk_assessment @device @medication_statement @service_request @diagnostic_report

Scenario: Doctor with active approval can read all the data of specified in approval episodes

Given Active approval on episode

When I require read access

Then I can read

Based on approvalepisodeby idnoneepisode.id in approvals.permitted_resources selected from DB 





encounter
episode








observation









condition








allergy_intolerance








immunization











@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 idencountercontext.origin_episode.managing_organization==token.client_id















by id: selected from DB

by search param: {encounter_id} from URL

by search param
condition by id
by search param
allergy_intolerance by id
by search param
immunization by id
by search param
risk_assessment by id
by search param
deviceby id
by search param
medication_statement by id
by search param
diagnostic_reportby idencounter.origin_episode.managing_organization==token.client_id
by search param














  • No labels