microsoft / microsoft/fhir-server
Add support for updated member-match operation
Open
VSTS-Backlog
- Dominant language
- TSQL
- Stars
- 1.4k
- Forks
- 592
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 41
Description
**User story**
As a user, I want to be able to use the $member-match operations in FHIR as defined in the updated HRex implemenation: https://build.fhir.org/ig/HL7/davinci-ehrx/OperationDefinition-member-match.html
**Acceptance criteria**
I can use the $member-match with consent
Contributor guide
Research direction
Start by reading the linked HRex OperationDefinition for the updated $member-match operation and compare its requirements with the server's current behavior. Trace the existing $member-match entry point and related consent handling; done means a member-match request with consent works according to the updated specification.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100