Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-37361

Clarify intent of onlyCertainMatches, and consider onlySingleMatch option

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • FHIR Core (FHIR)
    • R5
    • Patient Administration
    • Patient
    • Hide

      Add a new onlySingleMatch parameter.

      Name: onlySingleMatch

      Cardinality: 0..1

      Type: boolean

      Documentation:  If there are multiple potential matches, the server should identify the single most appropriate match that should be used with future interactions with the server (for example, as part of a subsequent create interaction).

       

      We will also update the Documentation for onlyCertainMatches to:

      If there are multiple potential matches, the server should be certain that each of the records are for the same patients.  This could happen if the records are duplicates, are the same person for the purpose of data segregation, or other reasons.  When false, the server may return multiple results with each result graded accordingly.

      Show
      Add a new onlySingleMatch parameter. Name : onlySingleMatch Cardinality : 0..1 Type : boolean Documentation :  If there are multiple potential matches, the server should identify the single most appropriate match that should be used with future interactions with the server (for example, as part of a subsequent create interaction).   We will also update the Documentation for onlyCertainMatches to: If there are multiple potential matches, the server should be certain that each of the records are for the same patients.  This could happen if the records are duplicates, are the same person for the purpose of data segregation, or other reasons.  When false, the server may return multiple results with each result graded accordingly.
    • Brian Postlethwaite / Reinhard Egelkraut : 10-0-0
    • Enhancement
    • Compatible, substantive
    • R5

    Description

      There is some confusion over what the onlyCertainMatches parameter to Patient.$match means.  This was discussed on this zulip thread:https://chat.fhir.org/#narrow/stream/179254-patient-administration-WG/topic/.2FPatient.2F.24match

       

      It sounds like there are two different scenarios:

      1. A client asks the server to identify a single patient records that should be used for subsequent work (e.g. POST'ing an Observation, where Observation.subject is a reference to that patient).
      2. Identifying the set of Patient records that are "certian" matches for the given inputs.  This (I think) would be a set of Patient records that have been identified as the same person (i.e., are duplicates).

       

      It sounds like the intent of onlyCertainMatches was to meet #2, but we (Epic) and I think others have been interpreting it to mean #1.

      We should clarify the intent of onlyCertainMatches, and possibly add a new onlySingleMatch to support scenario #1 above.

      Attachments

        Activity

          People

            brian.postlethwaite Brian Postlethwaite
            cooper.thompson Cooper Thompson
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: