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

Change "ID" to "IDs"

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • US Specialty Rx (FHIR)
    • 2.0.0-ballot
    • Pharmacy
    • Patient Matching
    • Hide

      The commenter identified wording that we agree is unclear... though the IG's intended meaning was different from what the commenter suggests.

      In the process described by this section, the data consumer performs a patient match to obtain the data source's Patient resource. The intent of the wording in question is that the data consumer shall include that Patient resource's ID (Patient.id) in subsequent queries.

      In response, these are changes to the section's referenced by the commenter to clarify the intent (changes italicized):

      • Pre-Match the Patient and include the Data Source's Patient resource ID (Patient.id) in RESTful searches or Specialty Rx Query message
      • When retrieving information using RESTful searches…
        • the Data Consumer system SHALL include a patient parameter in the search containing the retrieved Patient resource ID (Patient.id).
      • SHALL append a patient parameter containing the responder’s Patient resource ID (Patient.id) to each search string supplied in a query-string parameter in the request
      Show
      The commenter identified wording that we agree is unclear... though the IG's intended meaning was different from what the commenter suggests. In the process described by this section, the data consumer performs a patient match to obtain the data source's Patient resource. The intent of the wording in question is that the data consumer shall include that Patient resource's ID (Patient.id) in subsequent queries. In response, these are changes to the section's referenced by the commenter to clarify the intent (changes italicized): Pre-Match the Patient and include the Data Source's Patient resource ID (Patient.id) in RESTful searches or Specialty Rx Query message When retrieving information using RESTful searches… the Data Consumer system SHALL include a  patient parameter in the search containing the retrieved P atient resource ID (Patient.id) . SHALL append a patient parameter containing the responder’s P atient resource ID (Patient.id) to each search string supplied in a query-string  parameter in the request
    • Frank McKinney / John Hatem : 6-0-0
    • Clarification
    • Non-substantive

    Description

      Existing text:
      Pre-Match the Patient and include the Data Source's Patient resource ID in RESTful searches or Specialty Rx Query message.
      ..........
       
      When retrieving information using RESTful searches...
      the Data Consumer system SHALL include a patient parameter in the search containing the retrieved patient ID.
       
      ...............
      SHALL append a patient parameter containing the responder's patient ID to each search string supplied in a query-string parameter in the request.
       
      .....................
      patient's medical record number at the ordering practice.
       
      Suggested text:
       
      IDs, identifiers
       
      Ballot comment:
       
      Recommend changing all instances of "ID" to the plural "IDs" where appropriate to allow multiple patient identifiers to be included (when available) in order to support patient matching across entities. Medical record numbers may or may not be meaningful beyond the prescriber's EHR or electronic prescribing system, but other identifiers such as a social security number or subscriber number may be. 

      Attachments

        Activity

          People

            Unassigned Unassigned
            carmela_couderc Carmela A. Couderc
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: