microsoft / microsoft/fhir-server

Restrict Resources and Operations available and reflect restrictions in capability statement

Open
#2,082 5 comments 0 reactions 0 assignees View on GitHub
Epic VSTS-Backlog
Dominant language
TSQL
Stars
1.4k
Forks
592
Avg merge
2d 7h
Merged PRs (30d)
41

Description

Hi,

We're evaluating FHIR servers, got this R4 project running and working, but our use case is very specific for our initial rollout. We just want to allow for read operations on DiagnosticReport resources (maybe patient and other related resources as well). But I'm having a hard time figuring out how do we customize the R4 projects to get a paired down capability statement to reflect only allowing Http Gets on diagnostic reports?

Is this kind of customization built into the current code base? If so what is the intended way to accomplish this?

Thanks,
Chris

Contributor guide

Open the contributing guide

Research direction

Start by locating the R4 project’s configuration for enabled resources and operations and the code that generates the capability statement; the issue does not name files or entry points. Determine whether read-only DiagnosticReport access and related-resource restrictions are supported, and define completion as an implemented configuration path whose capability statement reflects the allowed operations.

Written by the indexing model from the issue text.

Assessment

Domain
api, backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.