Page Comparison

Rule: @rule_2

by id

person_id from JustificationFilter schema

There is an active token & an active justification

encounter

observation

condition

allergy_intolerance

immunization

risk_assessment

device

medication_statement

medication_request

medication_dispense

service_request

diagnostic_report

procedure

medication_administration

care_plan

activity

episode	DB.encounter.episode	episode.managing_organization==token.client_id
	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
observation	by id		episode	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
condition	by id		episode	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
service_request	by id		episode	DB.service_request.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
diagnostic_report	by id		episode	DB.diagnostic_report.encounter.episode
	by search params			context_episode_id from URL (path)
procedure	by id		episode	DB.procedures.encounter.episode
	by search params			search param {episode_id} from URL
medication_administration	by id		episode	IF context is encounter THEN: DB.medication_administrations.context.episode
	by search params			search param {episode_id} from URL
device	by id		episode	IF context is encounter THEN: DB.devices.context.episode
	by search params			search param {episode_id} from URL
risk_assessment	by id		episode	IF context is encounter THEN: DB.risk_assessments.context.episode
	by search params			search param {episode_id} from URL
medication_statement	by id		episode	IF context is encounter THEN: DB.medication_statements.context.episode
	by search params			search param {episode_id} from URL
immunization	by id		episode	IF context is encounter THEN: DB.immunizations.context.episode
	by search params			search param {episode_id} from URL
allergy_intolerance	by id		episode	IF context is encounter THEN: DB.allergy_intolerances.context.episode
	by search params			search param {episode_id} from URL
medication_request	by id		episode	DB.medication_request.context_episode_id
	by search params			search param {episode_id} from URL
medication_dispense	by id		episode	DB.medication_request.context_episode_id
	by search params			search param {episode_id} from URL
medication_request_request	by id		episode	DB.medication_request_request.context_episode_id
	by search params			search param {episode_id} from URL
clinical_impression	by id		episode	DB.clinical_impression.context_episode_id
	by search params			search param {episode_id} from URL
device_request	by search params	episode	search param {context_episode_id} from URL	episode.managing_organization==token.client_id
	by id (details in person context)		DB.device_requests.context_episode_id	device_requests.context_episode_id.managing_organization==token.client_id
device_dispense	by search params in patient context	episode	search param {context_episode_id} from URL	episode.managing_organization==token.client_id
	by id (details in person context)		DB.device_dispenses.context_episode_id	device_dispenses.context_episode_id.managing_organization==token.client_id

Rule: @rule_4 \| Action: @read
Scenario:	Base	Resource	Routes	Context	Source of context	Logic
Employee with active approval can read

entity created in the employee's MSP
Given Entity has been created on my MSP

When I require read access

Then I can read

Based on managing organization

service_request

by id

requester_legal_entity
+ patient_id

DB.service_request.managing_organization

managing_organization==id

by search param

search param {managing_organization} from URL

managing_organization (requester_legal_entity, )==token.client_id

episode
diagnostic_report
procedures
encounter
condition
observation

by id

managing_organisation + patient_id

DB.episode.managing_organization OR DB.diagnostic_report.managing_organization

managing_organization==id

by search param

search param {requester_legal_entity} from URL

managing_organization (requester_legal_entity, )==token.client_id

care_plan

managing_organisation

DB.care_plan.managing_organization

managing_organization ==token.client_id

activity

by activity id

managing_organisation

DB.care_plan.managing_organization

managing_organization ==token.client_id

search param {managing_organization_id} from URL

medication_request_request

& medication_request &
medication_dispense

by id

legal_entity + patient_id

search param {legal_entity_id} from URL

legal_entity_id==id

by search param

legal_entity_id==token.client_id

device_requests

requester_legal_entity

search param {requester_legal_entity} from URL

requester_legal_entity==token.client_id

DB.device_requests.requester_legal_entity

requester_legal_entity==token.client_id

Rule: @rule_3 | Action: @read

Scenario:

Base

Resource

Routes

Context*

Source of context

Logic

Employee can read all the data of episodes created in the employee's 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

episode

DB.encounter.episode

episode.managing_organization==token.client_id

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

observation

by id

episode

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

condition

by id

episode

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

service_request

by id

episode

DB.service_request.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

diagnostic_report

by id

episode

DB.diagnostic_report.encounter.episode

by search params

context_episode_id from URL (path)

procedure

by id

episode

DB.procedures

all the data (including merged persons/prepersons data) of specified in approval patient Given Active approval on patient When I require read access Then I can read	Based on patient_id	episode	by id	patient_id	patient_id from URL	There is an active approval on patient’s data granted to the to the employee (one of user's employee) in MongoDB
			by search params
			active diagnosis
			short episodes by search params
			by patient_id in observation context
			by patient_id in condition context
			by patient_id in procedure context
			by patient_id in diagnostic_report context
		encounter	by id
			by search params
			by id in episode context
			by search params in episode context
			short encounters by search params
			short encounters by ID
		observation	by id
			by search params
			short observations by search params
			short observation by id
		condition	by id
			by search params
			short conditions by search params
			short conditions by id
		service_request	list in episode context
			by search params
			by id in episode context
			by id
			by requisition
		procedure	by id
			by search params
			short procedures by id
			short procedures by search params
		diagnostic_report	by id
			by search params
			approved by patient_id
			short diagnostic_reports by search params
			by patient_id in observation context
			short diagnostic_reports by id
		care_plan	by id
			by search params
			by requisition
			by activity id
		activity	by id
		activity	by search params
		clinical_impression	by id
		clinical_impression	by search params
		medication_request_request	by id
		medication_request_request	by search params
		medication_request	by id
		medication_request	by search params
		medication_dispense	by id (details in person context)
		medication_dispense	by search params (by medication request id)
		device_request	by search params
		device_request	by id (details in person context)
		device_dispense	by search params in patient context
		device_dispense	by id (details in person context)

Rule: @rule_5 \| Action: @read
Scenario:	Base	Resource	Routes	Context*	Source of context	Logic
Employee with active approval or employees from legal_entity 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		http://DB.episode.id	There is an active approval on the episode granted to the employee (one of user's employee) OR to the legal_entity (one of legal_entity's employee) in MongoDB
		encounter	by id	episode	DB.encounter.episode
			by search params		search param {episode_id} from URL

medication_administration

by id in episode context	episode_id from URL (path)
by search params in episode context
observation	by id	episode

IF context is encounter THEN:

DB.

medication_administrations

observation.

context.

episode
by search params	search param {episode_id} from URL

device

by id

in episode

IF

context

is encounter THEN:

DB.devices.context.episode

episode_id from URL (path)
	by search params

search param {episode_id} from URL

risk_assessment

in episode context
condition	by id	episode

IF context is encounter THEN:

DB

.risk_assessments

.

context

condition.episode
by search params	search param {episode_id} from URL

medication_statement

by id in episode context	episode_id from URL (path)
by search params in episode context
service request	by id	episode

IF context is encounter THEN:

DB.

medication

service_

statements

requset.

context

encounter.episode
by search params	search param {episode_id} from URL

immunization


by id in episode context	episode

IF context is encounter THEN:
DB.immunizations.context

_id from URL (path)
	by search params in episode context
diagnostic_report	by id	episode	DB.diagnostic_report.encounter.episode
	by search params		search param {episode_id} from URL

allergy

medication_

intolerance

administration

by id

episode

IF context is encounter THEN:
DB.

allergy

medication_

intolerances

administrations.context.episode
by search params	search param {episode_id} from URL

medication_request

procedure

by id

episode

DB.

medication_request.context_episode_id

procedures.encounter.episode
by search params	search param {episode_id} from URL


medication_request & medication_dispense	by id	episode	DB.medication_request.context_episode_id
	by search params		search param {episode_id} from URL (can be used with {encounter_id} search param for sort by encounter)
medication_request_request	by id	episode	DB.medication_request_request.context_episode_id
	by search params		search param {episode_id} from URL (can be used with {encounter_id} search param for sort by encounter)
clinical_impression	by id	episode	DB.clinical_impression.context_episode_id
	by search params		search param {episode_id} from URL (can be used with {encounter_id} search param for sort by encounter)
device_

requests

request

episode

search param {context_episode_id} from URL

episode.managing_organization==token.client_id


by id (details in person context)	DB.device_requests.context_episode

_iddevice_requests

_id
device_dispense	by search params in patient context	episode	search param {context_episode_id} from URL
device_dispense	by id (details in person context)	episode	DB.device_dispenses.context_episode

_id.managing_organization==token.client

_id

Rule: @rule_

4

6 | Action:

@read

@read
Scenario:	Base	Resource	Routes	Context*	Source of context	Logic

Employee 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

Based on patient_id

episode

patient_id

patient_id from URL

There is an active approval on patient’s data granted to the to the employee (one of user's employee) in MongoDB

short episodes by search params

active diagnosis

by patient_id in observation context

by patient_id in condition context

by patient_id in procedure context

by patient_id in diagnostic_report context

encounter

by search params in episode context

by id in episode context

short encounters by search params

short encounters by ID

observation

short observations by search params

short observation by id

condition

short conditions by search params

short conditions by id

service_request

list in episode context

short procedures by search params

by id in episode context

procedure

short procedures by id

diagnostic_report

short diagnostic_reports by search params

approved by patient_id

by patient_id in observation context

short diagnostic_reports by id

care_plan

activity

clinical_impression

by id

by search params

medication_request_request

by id

by search params

medication_request

by id

by search params

medication_dispense

by id (details in person context)

by search params (by medication request id)

device_requests

Rule: @rule_5 | Action: @read

Scenario:

Base

Resource

Routes

Context*

Source of context

Logic

Employee with active approval or employees from legal_entity 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

DB.episode.id

There is an active approval on the episode granted to the employee (one of user's employee) OR to the legal_entity (one of legal_entity's employee) in MongoDB

encounter

by id

episode

DB.


Employee can read entity originated by episode created in the employee's legal entity Given Entity has been originated by mine legal entity episode When I require read access Then I can read	Based on origin episode	encounter	by id	origin_episode	DB.encounter.origin_episode	origin_episode.managing_organization==token.client_id
			by search params		Search param {origin_episode_id} from URL
		diagnostic repost	by id	origin_episode	DB.diagnostic_report.origin_episode
			by search params		Search param {origin_episode_id} from URL
		procedures	by id	origin_episode	DB.procedures.encounter.episode
			by search params		search param {episode_id} from URL
		device_dispense	by search params in patient context	origin_episode	Search param {origin_episode_id} from URL
			by id (details in person context)		DB.device_dispense.origin_episode_id

Rule: @rule_7 \| Action: @read
Scenario:	Base	Resource	Routes	Context*	Source of context	Logic
Employee can read all the data of diagnostic report originated by episode created in the employee's legal entity Given Diagnostic report context has been originated by mine legal entity episode When I require read access Then I can read	Based on origin episode	observation	by id	diagnostic_report	DB.observation.diagnostic_report.origin_episode	origin_episode.managing_organization==token.client_id
			by search params		Search param {diagnostic_report_id} from URL

Rule: @rule_8 \| Action: @read
Scenario:	Base	Resource	Routes	Context*	Source of context	Logic
Employee can read all the data of encounter originated by episode created in the employee's legal entity Given Encounter context has been originated by mine legal entity episode When I require read access Then I can read	Based on origin episode	observation	by id	encounter	DB.observation.context.origin_episode	origin_episode.managing_organization==token.client_id
			by search params		Search param {encounter_id} from URL
		condition	by id	encounter	DB.condition.context.origin_episode
			by search params		Search param {encounter_id} from URL
		diagnostic_report	by id	encounter	DB.diagnostic_report.encounter.origin_episode
			by search params		Search param {encounter_id} from URL
		medication_administration	by id	encounter	IF context is encounter THEN: DB.medication_administrations.context.encounter
			by search params		search param {encounter_id} from URL
		procedure	by id	encounter	DB.procedures.encounter.episode
			by search params		search param {

episode

encounter_id} from URL
~~medication_request~~	~~by id~~

in episode context

episode_id from URL (path)

by search params in episode context

observation

	~~encounter~~	~~DB.medication_request.context~~
~~by search params~~	~~encounter~~	~~search param {encounter_id} from URL~~
~~medication_request_request~~	~~by id~~

episode

~~encounter~~

~~DB.~~

observation.episode

~~medication_request_request.context~~
~~by search params~~	~~search param {encounter_id} from URL~~
device_dispense	by search params

search param {episode

in patient context	encounter	Search param {encounter_id} from URL
by id (details in	encounter

episode

person context)

episode_id from URL (path)

by search params in episode context

condition

by id

episode

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

service request

by id

episode

DB.service_requset.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

diagnostic_report

by id

episode

DB.diagnostic_report.encounter.episode

by search params

search param {episode_id} from URL

medication_administration

by id

episode

IF context is encounter THEN:
DB.medication_administrations.context.episode

by search params

search param {episode_id} from URL

procedure

by id

episode

DB.procedures.encounter.episode

by search params

search param {episode_id} from URL

medication_request & medication_dispense

by id

episode

DB.medication_request.context_episode_id

by search params

search param {episode_id} from URL (can be used with {encounter_id} search param for sort by encounter)

medication_request_request

by id

episode

DB.medication_request_request.context_episode_id

by search params

search param {episode_id} from URL (can be used with {encounter_id} search param for sort by encounter)

clinical_impression

by id

episode

DB.clinical_impression.context_episode_id

by search params

search param {episode_id} from URL (can be used with {encounter_id} search param for sort by encounter)

device_requests

episode

search param {context_episode_id} from URL

DB.device_requests.context_episode_id

Rule: @rule_6 | Action: @read

DB.device_dispense.encounter.origin_episode_id

Rule: @rule_9 \| Action: @read \| NOT IMPLEMENTED YET
Scenario:	Base	Resource	Routes	Context	Source of context	Logic
Employee with active approval can read data, originated by the episode Given Active approval on patient When I require read access Then I can read		encounter
		observation
		condition
		service_request
		diagnostic_report

Rule: @rule_10 \| Action: @read
Scenario:	Base	Resource	Routes	Context*	Source of context	Logic
Employee can read all the data of diagnostic report created in the employee's legal entity Given Diagnostic report context has been originated by mine legal entity When I require read access Then I can read	Based on diagnostic report	observation	by id	diagnostic_report	DB.observation.diagnostic_report.managing_organization	diagnostic_report.managing_organization==token.client_id
			by search params		Search param {diagnostic_report_id} from URL

Rule: @rule_11 \| Action: @read
Scenario:	Base	Resource	Routes	Context*	Source of context	Logic
Employee with active approval or employees from legal_entity 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	diagnostic_report	by id	diagnostic_report	DB.diagnostic_report	There is an active approval on the diagnostic report granted to the employee (one of user's employee) OR to the legal_entity (one of legal_entity's employee) in MongoDB
		observation	by id	diagnostic_report	DB.observation.diagnostic_report.managing_organization
		observation	by search params	diagnostic_report	Search param {diagnostic_report_id} from URL

Rule: @rule_12 \| Action: @read
Scenario:	Base	Resource	Routes	Context

*

	Source of context	Logic
Employee with active approval can read

entity originated by episode created in the employee's MSP

Given Entity has been originated by mine MSP episode

When I

the data associated with the care plan

Given Active approval on care_plan

When I require read access

Then I

Then I can read

Based on

origin episodeencounter

care plan

care_plan

by id

origin_episode

care_plan + patient_id

DB.

encounter.origin_episodeorigin_episode.managing_organization==token.client_id

care_plan.id=approvals.granted_resources[].value	There is an active approval (access_level=read) on the care_plan granted to the employee by the patient (one of user's employee) in MongoDB
activity		by id	care_plan + patient_id	care_plan_id & patient_id from URL (path)
		by search params

Search param {origin_episode_id} from URL

diagnostic repost

medication_request_request

by id

origin_episode

DB.diagnostic_report.origin_episode

care_plan + patient_id	care_plan_id & patient_id from URL (path)
		by search params

Search param {origin_episode_id} from URL

procedures

by search params

search param {episode_id} from URL

Rule: @rule_7 | Action: @read

Scenario:

Base

Resource

Routes

Context*

Source of context

Logic

Employee can read all the data of diagnostic report originated by episode created in the employee's 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

DB.observation.diagnostic_report.origin_episode

origin_episode.managing_organization==token.client_id

by search params

Search param {diagnostic_report_id} from URL

Rule: @rule_8 | Action: @read

medication_request

by id

origin_episode

DB.procedures.encounter.episode

care_plan + patient_id	care_plan_id & patient_id from URL (path)
		by search params
medication_dispense	by id	care_plan + patient_id	care_plan_id & patient_id from URL (path)
	by search params
device_request	by id	care_plan	DB.device_request.based_on.care_plan[].id=approvals.granted_resources[].value
	by search params		care_plan & patient_id from URL (path)=approvals.granted_resources[].value.care_plan

Rule: @rule_13 \| Action: @write
Scenario:	Base	Resource	Routes	Context

*

	Source of context	Logic
Employee

can read all the data of encounter originated by episode created in the employee's 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

DB.observation.context.origin_episode

origin_episode.managing_organization==token.client_id

by search params

Search param {encounter_id} from URL

condition

by id

encounter

DB.condition.context.origin_episode

by search params

Search param {encounter_id} from URL

diagnostic_report

by id

encounter

DB.diagnostic_report.encounter.origin_episode

by search params

Search param {encounter_id} from URL

medication_administration

by id

encounter

IF context is encounter THEN:
DB.medication_administrations.context.encounter

by search params

search param {encounter_id} from URL

procedure

by id

encounter

DB.procedures.encounter.episode

by search params

search param {encounter_id} from URL

~~medication_request~~

~~by id~~

~~encounter~~

~~DB.medication_request.context~~

~~by search params~~

~~search param {encounter_id} from URL~~

~~medication_request_request~~

~~by id~~

~~encounter~~

~~DB.medication_request_request.context~~

~~by search params~~

~~search param {encounter_id} from URL~~

Rule: @rule_9| Action: @read | NOT IMPLEMENTED YET

with active write approval can write the data associated with the care plan Given Active write approval on care_plan When I require write access Then I can write	Based on care plan	care_plan	~~by id~~ Cancel	care_plan ~~+ patient_id~~	DB.care_plan.id=approvals.granted_resources[].value	There is an active approval (access_level=write) on the care_plan granted to the employee by the patient (one of user's employee) in MongoDB
			Complete
		activity	~~by id~~ Prequalify		~~care_plan_id & patient_id from URL (path)~~ care_plan_id from URL (path) =approvals.granted_resources[].value
			~~by search params~~ Create
			Cancel
			Complete
		~~medication_request_request~~	~~by id~~	~~care_plan + patient_id~~	~~care_plan_id & patient_id from URL (path)~~
			~~by search params~~
		~~medication_request~~	~~by id~~	~~care_plan + patient_id~~	~~care_plan_id & patient_id from URL (path)~~
			~~by search params~~
		~~medication_dispense~~	~~by id~~	~~care_plan + patient_id~~	~~care_plan_id & patient_id from URL (path)~~
			~~by search params~~
		device_request	by id	care_plan	DB.device_request.based_on.care_plan[].id=approvals.granted_resources[].value
			by search params		care_plan & patient_id from URL (path)=approvals.granted_resources[].value.care_plan

Rule: @rule_14 \| Action: @read
Scenario:	Base	Resource	Routes	Context	Source of context	Logic
Employee with active approval on the care plan can read

data, originated by the episode Given Active approval on patientWhen I

the data based on this care plan

Given Entity based on care_plan

When I require read access

Then I

Then I can read

encounter

observation

condition

service_request

diagnostic_report

Rule: @rule_10 | Action: @read

Scenario:

Base

Resource

Routes

Context*

Source of context

Logic

Employee can read all the data of diagnostic report created in the employee's 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

DB.observation.diagnostic_report.managing_organization

diagnostic_report.managing_organization==token.client_id

by search params

Search param {diagnostic_report_id} from URL

Rule: @rule_11 | Action: @read

Scenario:

Base

Resource

Routes

Context*

Source of context

Logic

Employee with active approval or employees from legal_entity 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

DB.observation.diagnostic_report.managing_organization

There is an active approval on the diagnostic report granted to the employee (one of user's employee) OR to the legal_entity (one of legal_entity's employee) in MongoDB

by search params

Search param {diagnostic_report_id} from URL

Rule: @rule_12

Based on care plan	service_request	by id	care_plan (based_on) + patient_id	DB.service_request.based_on.care_plan[].id=approvals.granted_resources[].value	There is an active approval (access_level=read/~~write~~) on the care_plan granted to the employee by the patient (one of user's employee) in MongoDB
	service_request	by search params	care_plan + patient_id	care_plan_id from URL (search param) & patient_id from path
	encounter	by id	patient_id ->. care_plan (based_on service_request)	DB.encounter.based_on.service_request.based_on.care_plan[].id=approvals.granted_resources[].value OR DB.diagnostic_report.based_on.service_request.based_on.care_plan[].id=approvals.granted_resources[].value OR DB.procedure.based_on.service_request.based_on.care_plan[].id=approvals.granted_resources[].value
	diagnostic_report	by id
	procedure	by id
	device_dispense	by id (details in person context)	care_plan (based_on device_request)	DB.device_dispense.based_on.device_request.based_on.care_plan[].id=approvals.granted_resources[].value

Rule: @rule_15 \| Action: @read
Scenario:	Base	Resource	Routes	Context*	Source of context	Logic
Employee with

active

verified unexpired approval on procedure can read all the data

associated with the care plan

Given Active approval on care_plan

When I

of this procedure

Given Active approval on procedure

When I require read access

Then I

Then I can read

Based on

care plancare_plan

procedure

by id

care_plan + patient_id

procedure

DB.procedures.

care

_

plan.

id

=approvals.granted_resources[].value

There is

an active approval (access_level=read) on the care_plan

a verified unexpired approval on procedure granted to the employee

by the patient

(one of user's employee) in MongoDB

activity

by id

care_plan + patient_id

care_plan_id & patient_id from URL (path)

by search params

medication_request_request

by id

care_plan + patient_id

care_plan_id & patient_id from URL (path)

by search params

medication_request

by id

care_plan + patient_id

care_plan_id & patient_id from URL (path)

by search params

medication_dispense

by id

care_plan + patient_id

care_plan_id & patient_id from URL (path)

by search params

Rule: @rule_13 | Action: @write

Rule: @rule_16 \| Action: @read
Scenario:	Base	Resource	Routes	Context*	Source of context	Logic

Rule: @rule_17 \| Action: @read
Scenario:	Base	Resource	Routes	Context*	Source of context	Logic
Employee

with active approval

can

write

read all the data associated with the care plan

Given Active approval on care_plan

When I require write access

Then I can write

created in the employee's legal entity

Given Care plan has been created on my legal entity

When I require read access

Then I can read

Based on care plan

care_plan

activity

care_plan+ patient_id

DB.activities.care_plan[].id

care_plan.managing_organization.id==

approvals

token.

granted_resources[].value

There is an active approval (access_level=write) on the care_plan granted to the employee by the patient (one of user's employee) in MongoDB

activity

by id

care_plan + patient_id

client_id
	by search params	care_plan_id from URL (search param) & patient_id from path
	medication_request_request	by id	DB.medication_request_request.based_on.care_plan[].id
		by search params	care_plan_id from URL (search param) & patient_id from

URL (

path

)

by search params

medication_request_request

by id

care_plan + patient_id


list in care plan context	care_plan_id &

patient

person_id from URL (

path

search param)

by search params

medication_request