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

Include prescription patient identifier in patient-match [added]

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive with Modification
    • Icon: Highest Highest
    • US Specialty Rx (FHIR)
    • 0.1.0 [deprecated]
    • Pharmacy
    • Systematic Query Workflows
    • Hide

      Propose adding content to the Patient Matching page:

      • Clarify the nature of the patient medical record identifier in the NCPDP NewRx message
        • The NewRx message does not contain the patient FHIR resource ID 
        • The patient MRN element that a pharmacy can recieve in an NCPDP NewRx (MedicalRecordIdentificationNumberEHR) does not contain the system associated with the MRN ID
        • The maximum length of the NewRx MRN element is 35 characters, preventing its use by some systems that maintain longer medical record numbers

       

      •  Recommend including the value from MedicalRecordIdentificationNumberEHR that was received in the NewRx when submitting a patient-match operation
        • Include Identifier.type = MR (medical record number)
        • Include identifier.type.text = "MRN from prescription"
        • Include data-absent-reason extension in place of the mandatory identifier.system element, with value "unknown"
        • Note that when sent with the MR identifier type in this use case, the identifier represents the MRN from the NewRx
      Show
      Propose adding content to the Patient Matching page: Clarify the nature of the patient medical record identifier in the NCPDP NewRx message The NewRx message does not contain the patient FHIR resource ID  The patient MRN element that a pharmacy can recieve in an NCPDP NewRx (MedicalRecordIdentificationNumberEHR) does not contain the system associated with the MRN ID The maximum length of the NewRx MRN element is 35 characters, preventing its use by some systems that maintain longer medical record numbers    Recommend including the value from MedicalRecordIdentificationNumberEHR that was received in the NewRx when submitting a patient-match operation Include Identifier.type = MR (medical record number) Include identifier.type.text = "MRN from prescription" Include data-absent-reason extension in place of the mandatory identifier.system element, with value "unknown" Note that when sent with the MR identifier type in this use case, the identifier represents the MRN from the NewRx
    • Frank McKinney / Tim McNeil : 11-0-3
    • Clarification
    • Non-substantive

    Description

      Using $match introduces a heavy-weight operation in the information exchange flow, which is not necessary, given that the patient identifier must be part of the prescription message. At the very least, clarify that the data consumer must use the patient identifier from the prescription message.

      Existing Wording:

      Use of $match

      Proposed Wording:

      The prescription message shall have the patient identifier to be used directly in the RESTful search

      (Comment 19 - imported by: Jean Duteau)

      Attachments

        Activity

          People

            Unassigned Unassigned
            vassil Vassil Peytchev
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: