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.

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

FHIR Core Updates for OnlySingleMatch #112

Open
slagesse-epic opened this issue Oct 26, 2023 · 0 comments
Open

FHIR Core Updates for OnlySingleMatch #112

slagesse-epic opened this issue Oct 26, 2023 · 0 comments
Labels
open-issue Documented as an Open-Issue

Comments

@slagesse-epic
Copy link
Member

The onlyCertainMatches parameter may be optionally set to true to indicate that the Patient Demographics Consumer would only like matches returned when they are certain to be matches for the subject of the request.

The Patient Demographics Consumer might want to use onlyCertainMatches to prevent multiple Patient Resources from being returned in the response. This is often necessary in B2B cases where the Patient Demographics Consumer is operating in the background without a user confirming the Patient match.

However, onlyCertainMatches does not guarantee that only a single Patient Resource will be returned. There might still be multiple results returned in the response when the same person has multiple records in the Patient Demographics Supplier. FHIR-37361 and FHIR-40880 request an additional parameter for specifying that matches should only be returned when there is exactly 1 certain match.

When updating PDQm to a version of FHIR with FHIR-37361 and FHIR-40880 applied, the new parameter will need to be incorporated into the ITI-119 transaction.

@slagesse-epic slagesse-epic added the open-issue Documented as an Open-Issue label Oct 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
open-issue Documented as an Open-Issue
Projects
None yet
Development

No branches or pull requests

1 participant