Closed JohnMoehrke closed 1 year ago
I think this distinction is already covered by the comparison in section 1:38.1.2.3. In particular, the bullet points are intended to help the reader through this line of thinking.
Are you finding something confusing or lacking about that section?
I found this comment by Cooper to be helpful, and possibly help us distinguish between search and $match in our work.
Cooper Thompson 9:57 AM This isn't US Core's position, but I've generally suggested that you use Patient.search when you have an end user in front of a keyboard doing a search, and that end user can review the (possibly) multiple results and select the right one based on interaction with the patient or other information the user knows about the patient.
You'd use $match when you need to do a system-to-system query and need to get exactly one high threshold match to use in subsequent automated API calls (with no human in the loop).
There is some fuzziness here, like you could use $match for user-facing searching as well, but in general this is how I think of $match vs. Patient.search.