microsoft / microsoft/fhir-server
Granular consent management using FHIR consents
Nobody has claimed this yet.
- Dominant language
- TSQL
- Stars
- 1.4k
- Forks
- 592
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 41
Description
I would like to know how to do more granular consent management. "Patient x gives crud permission to Practitioner y" sort of permissions.
Examples:
- In the Google Healthcare API there is a [preview feature](https://cloud.google.com/healthcare-api/docs/fhir-consent) that allows this sort of Consent Management.
- https://smilecdr.com/docs/security/consent_service.html
The only issue that I have found is #1182, which refers to the [FHIR Proxy](https://github.com/microsoft/fhir-proxy). They used to describe a [Consent Opt-Out filter](https://github.com/microsoft/fhir-proxy?tab=readme-ov-file#consent-opt-out-filter) that did exactly this. But unfortunately the proxy has been deprecated since. What is currently the supported way of achieving this?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file, test, or entry point is named. Start by reviewing issue #1182 and the current FHIR server documentation, then compare the requested Patient-to-Practitioner CRUD permissions with the referenced FHIR Consent approaches. Done would be identifying and documenting a supported implementation path, or clearly defining the missing feature.
Written by the indexing model from the issue text.
Assessment
- Domain
- authorization, security
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100