Add endpoint to check auto, potential,conflict matches #128
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
reagan-meant
changed the title
reagan-meant
commented
Oct 17, 2023
server/lib/routes/match.js
Outdated
| @@ -982,6 +982,215 @@ router.get(`/count-match-issues`, (req, res) => { | |||
| }); | |||
| }); | |||
|
|
|||
| router.post('/potential-matches', (req, res) => { | |||
There was a problem hiding this comment.
@azizdiakite could you rename this to 'matches' instead of 'potential-matches'
ashaban
approved these changes
Mar 12, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Add an endpoint to get potential, auto and conflict matches without creating the patient first.
This post request expects a fhir patient object to be passed in.
Unfortunately we can't just modify the current apis since this returned three types of matches and not only potential matches