Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Not-allowed literal reference seems unnecessary strict #251

Open
jkiddo opened this issue Jan 24, 2025 · 2 comments
Open

Not-allowed literal reference seems unnecessary strict #251

jkiddo opened this issue Jan 24, 2025 · 2 comments

Comments

@jkiddo
Copy link

jkiddo commented Jan 24, 2025

Why are patient literal references not allowed in the consents

ch-epr-fhir/input/fsh/ppqm_consent.fsh

Line 57 in e696fd2

* patient.reference 0..0
?
@oliveregger
Copy link
Collaborator

the original motivation was to define a 1 to 1 mapping from the Consent to the XACML Policy without any intermediate conversion steps. is this an issue?

@jkiddo
Copy link
Author

jkiddo commented Jan 30, 2025

Yes, its an issue when you are a FHIR-first platform. Logically it means the same, hence there shouldnt be that kind of restriction

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jkiddo @oliveregger