Page Comparison

...

@rule_-1

@read @allergy_intolerance @immunization @risk_assessment @device @medication_statement

Scenario: Employee can read insensitive patient’s data

...

Rule base type	Description
Based on declaration	Doctor with an active declaration can access all the patient's medical data.
Based on managing organization	User can read entities, created in his MSP
Based on context episode	User can read medical data, that was collected during an episode of care, that user has access to.
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 origin episode	Doctor can read medical data, that was collected as a part of a diagnostic report or episode of care, that user has access to. Episode of care, that contains this service request, is considered as an origin episode in that case.

on user tokenThere is an active token given by Cabinet to a patient1 @encounter @observation @condition report @procedures @medication_administration 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
patient_id
There is an active declaration between the patient and the doctor in OPS
patient_id from URL
encounter
observation
by search params2 @episode @service_request @diagnostic_report @procedures entity Entity managing organization
managing_organization==token.client_id
DB.episode.managing_organizationservice requestdiagnostic_reportepisode
episode.managing_organization==token.client_id
observationepisode_id from URL (path)DB.service_request.encounterdiagnostic_report

Rule	Base	Resource	Routes	Context	Logic	Source of context
@rule_-1 @read @allergy_intolerance @immunization @risk_assessment @device @medication_statement Scenario: Employee can read insensitive patient’s data Given User access token with client_type not equal to cabinet When I require read access Then I can read	Based on user token		by id		There is an active token
	Based on user token		by search params		There is an active token
@rule_0 @read @episode @encounter @observation @condition@service_request @diagnostic_report @procedures @allergy_intolerance @immunization @risk_assessment @device @medication_statement @procedure @medication_administration Scenario: Patient can read it's own data Given Patient has access_token given by Cabinet When I require read access Then I can read	Based on patient token		by id	patient_id	There is an active token given by Cabinet to a patient
	Based on patient token		by search params	patient_id	There is an active token given by Cabinet to a patient
@rule_1 @read @episode @encounter @observation @condition @service_request @diagnostic_report @procedures @medication_administration 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_id	There is an active declaration between the patient and the doctor in OPS	patient_id from URL
			episode	by search params
			encounter	by id
				by search params
				by id in episode context
				by search params in episode context
			observation	by id				There is an active token
				by search params				There is an active token	@rule_0 @read @episode @encounter @observation @condition@service_request @diagnostic_report @procedures @allergy_intolerance @immunization @risk_assessment @device @medication_statement @procedure @medication_administration Scenario: Patient can read it's own data Given Patient has access_token given by Cabinet When I require read access Then I can read	Based on patient token	by id	patient_id
				by id in episode context						Based on patient token		patient_id
				by search params in episode context
			condition	by id
				by search params
				by id in episode context
				by search params in episode context
			service_request	by id
			service_request	by search params
			diagnostic_report	by id
			diagnostic_report	by search params
			procedures	by search params
@rule_	2 @read @episode	@service_request @diagnostic_	report @procedures Scenario: Doctor	episode	by id
				episode	by search params
				by id
				by search params
				by id in episode context
				by search params in episode context
				by id
by search params
by id in episode context
by search params in episode context
condition	by id
	by search params
	by id in episode context
	by search params in episode context
service_request	by id
service_request	can read entity created in the doctors MSP Given Entity has been created on my MSP When I require read access Then I can read	Based on managing organization	episode	by id	episode	managing_organization==token.client_id	DB.episode.managing_organization
by search params			episode	search param {managing_organization} from URL	episode
service_request			by id	service request	DB.service_request.managing_organization
service_request			by search params	service request	search param {requester_legal_entity} from URL
diagnostic_report			by id	diagnostic_report	DB.diagnostic_report.managing_organization
diagnostic_report			by search params	diagnostic_report	search param {managing_organization} from URL
procedures			by search params	managing_organization	search param {managing_organization} from URL
@rule_	3 @read	@encounter @observation @condition @service_request @diagnostic_report, @devices, @medication_statements, @immunizations, @risk_assessments, @medication_administrations, @procedures Scenario: Doctor can read	all the data of episodes created in the doctors MSP Given	Episode context has been created on my MSP When I require read access Then I can read	Based on	episode	by id	episode	context episode	encounter	by id	episode	episode.managing_organization==token.client_id	DB.encounter.episode
						episode	by search params	episode			search param {episode_id} from URL
						by id in episode context	episode_id from URL (path)
						by search params in episode context	episode_id from URL (path)
						observation	by id	DB.observation.episode
							by search params	search param {episode_id} from URL
							by id in episode context	episode_id from URL (path)
							by search params in episode context	episode_id from URL (path)
						condition	by id	DB.condition.episode
							by search params	search param {managingepisode_organization} from URLid} from URL
							by is in episode context	episode_id from URL (path)
							by search params in episode context	episode_id from URL (path)
						service_request	by id			DB.service_request.encounter.episode.managing_organization
							by search params	search param {requester_legal_entity} from URLepisode_id} from URL
							by id in episode context	episode_id from URL (path)
						diagnostic_report	by id	id		DB.diagnostic_report.encounter.episode.managing_organization
						diagnostic_report	by search params	search param {managing_organization} from URL
						procedures	by search params	managing_organization		search param {managing_organization} from URL
						@rule_3 @read @encounter @observation @condition @service_request @diagnostic_report Scenario: Doctor can read all the data of episodes created in the doctors MSP Given Episode context has been created on my MSP When I require read access Then I can read	Based on context episode	encounter		by id	DB.encounter.episodecontext_episode_id from URL (path)
										medication_statement	by id			IF context is encounter THEN: DB.medication_statements.context.episode.managing_organization
										medication_statement	by search params			search param {episode_id} from URL
										immunization	by id			IF context is encounter THEN: DB.immunizations.context.episode.managing_organization
								by search params			search param {episode_id} from URL
								by id in episode context			episode_id from URL (path)
								by search params in episode context			episode_id from URL (path)
								device		by id	IF context is encounter THEN: DB.observationdevices.context.episode.managing_organization
								device		by search params	search param {episode_id} from URL
								risk_assessment		by id in episode context	episode_id from URL (path)
								risk_assessment		by search params in episode context	episode_id from URL (path)
								condition		by id	DB.condition.episode			IF context is encounter THEN: DB.risk_assessments.context.episode.managing_organization
										by search params	search param {episode_id} from URL			by is in episode context
by search params in episode context
service_request	by id	medication_administration	by id	IF context is encounter THEN: DB.medication_administrations.context.episode.managing_organization
	by search params	medication_administration	search param {episodeencounter_id} from URL	by id in episode context	??? (or extending of Search method with episode_id from URL (path)			param is needed)???
	procedure	by id	DB.diagnostic_reportprocedures.encounter.episode.managing_organization
by search params	procedure	context_search param {episode_id} from URL (path)
@rule_4 @read @episode @encounter @observation @condition @allergy_intolerance @immunization @risk_assessment @device @medication_statement @service_request @diagnostic_report @medication_administration Scenario: Doctor with active approval can read all the data of specified in approval patient Given Active approval on patient When I require read access Then I can read	not implemented yet
@rule_5 @read @episode @encounter @observation @condition @allergy_intolerance @immunization @risk_assessment @device @medication_statement @service_request @diagnostic_report @procedure @medication_administration 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 context episode	episode	by id	episode	There is an active approval on the episode granted to the employee (one of user's employee) in MongoDB	DB.episode.id
		encounter	by id			DB.encounter.episode
			by search params			search param {episode_id} from URL
			by id in episode context			episode_id from URL (path)
			by search params in episode context			episode_id from URL (path)
		observation	by id			DB.observation.episode
			by search params			search param {episode_id} from URL
			by id in episode context			episode_id from URL (path)
			by search params in episode context			episode_id from URL (path)
		condition	by id			DB.condition.episode
			by search params			search param {episode_id} from URL
			by id in episode context			episode_id from URL (path)
			by search params in episode context			episode_id from URL (path)
		service request	by id			DB.service_requset.encounter.episode
			by search params			search param {episode_id} from URL
			by id in episode context			episode_id from URL (path)
		diagnostic report	by id			DB.diagnostic_report.encounter.episode
		diagnostic report	by search params			search param {episode_id} from URL
		procedure	by id			DB.procedures.encounter.episode
		procedure	by search params			search param {episode_id} from URL
@rule_6 @read @diagnostic_report @encounter @procedure Scenario: Doctor can read entity originated by episode created in the doctors MSP Given Entity has been originated by mine MSP episode When I require read access Then I can read	Based on origin episode	encounter	by id	origin_episode	origin_episode.managing_organization==token.client_id	DB.encounter.origin_episode
		encounter	by search params			Search param {origin_episode_id} from URL
		diagnostic repost	by id			DB.diagnostic_report.origin_episode
		diagnostic repost	by search params			Search param {origin_episode_id} from URL
		procedures	by search params			DB.diagnostic_report.origin_episode
@rule_7 @read @observation Scenario: Doctor can read all the data of diagnostic report originated by episode created in the doctors MSP Given Diagnostic report context has been originated by mine MSP episode When I require read access Then I can read	Based on origin episode	observation	by id	diagnostic_report	origin_episode.managing_organization==token.client_id	DB.observation.diagnostic_report.origin_episode
	Based on origin episode	observation	by search params	diagnostic_report	origin_episode.managing_organization==token.client_id	Search param {diagnostic_report_id} from URL
@rule_8 @read @observation @condition @allergy_intolerance @immunization @risk_assessment @device @medication_statement @service_request @diagnostic_report @procedure @medication_administration 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 MSP episode When I require read access Then I can read	Based on origin episode	observation	by id	encounter	origin_episode.managing_organization==token.client_id	DB.observation.context.origin_episode
		observation	by search params			Search param {encounter_id} from URL
		condition	by id			DB.condition.context.origin_episode
		condition	by search params			Search param {encounter_id} from URL
		service request	by id			DB.service_request.encounter.origin_episode
		service request	by search params			Search param {encounter_id} from URL
		diagnostic_report	by id			DB.diagnostic_report.encounter.origin_episode
		diagnostic_report	by search params			Search param {encounter_id} from URL
		procedure	by id			DB.procedure.origin_episode
		procedure	by search params			Search param {encounter_id} from URL
@rule_9 @read @encounter @observation @condition @service_request @diagnostic_report Scenario: Doctor with active approval can read data, originated by the episode Given Active approval on episode When I require read access Then I can read	not implemented yet
@rule_10 @read @observation Scenario: Doctor can read all the data of diagnostic report created in the doctors MSP Given Diagnostic report context has been originated by mine MSP When I require read access Then I can read	Based on diagnostic report	observation	by id	diagnostic_report	diagnostic_report.managing_organization==token.client_id	DB.observation.diagnostic_report.managing_organization
	Based on diagnostic report	observation	by search params	diagnostic_report	diagnostic_report.managing_organization==token.client_id	Search param {diagnostic_report_id} from URL
@rule_11 @read @observation Scenario: Doctor with active approval can read all the data of specified in approval diagnostic report Given Active approval on diagnostic report When I require read access Then I can read	Based on diagnostic report	observation	by id	diagnostic_report	There is an active approval on the diagnostic report granted to the employee (one of user's employee) in MongoDB	DB.observation.diagnostic_report
	Based on diagnostic report	observation	by search params	diagnostic_report		Search param {diagnostic_report_id} from URL

...

Versions Compared

Old Version 27

New Version 28

Key