onlyCertainMatches | 0..1 | boolean |
|
| If there are multiple potential matches, then the match should not return the results with this flag set to true. When false, the server may return multiple results with each result graded accordingly. Recommendations to ONC/CMS: - Industry derived consensus based metrics for matching - transparency and clarity in how these are calculated
- How are multiple matches ranked? Are scores the best way to rank them?
- Should there be a national reference database that reflects the population of the nation as a whole, with regional variations accounted for, that matching services can use to demonstrate their ability to meet these metrics?
- Data Quality metrics should also be considered in addition to matching algorithm metrics
|
return | 1..1 | Bundle |
|
| A bundle contain a set of Patient records that represent possible matches, optionally it may also contain an OperationOutcome with further information about the search results (such as warnings or information messages, such as a count of records that were close but eliminated) If the operation was unsuccessful, then an OperationOutcome may be returned along with a BadRequest status Code (e.g. security issue, or insufficient properties in patient fragment - check against profile) Note: as this is the only out parameter, it is a resource, and it has the name 'return', the result of this operation is returned directly as a resource |