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

Medical Record Number and Patient Account Number

    XMLWordPrintableJSON

    Details

    • Type: Change Request
    • Status: Resolved - change required (View Workflow)
    • Priority: Medium
    • Resolution: Persuasive with Modification
    • Specification:
      US CARIN Blue Button (FHIR)
    • Raised in Version:
      1.0.0
    • Work Group:
      Financial Mgmt
    • Related Page(s):
      (NA)
    • Grouping:
    • Resolution Description:
      Hide

      Two new supportingInfo slices for IP, OP, and Professional EOB will be defined for medicalrecordnumber and patientaccountnumber.  We will create two new slices with a cardinality of (0..1) and marked as Must Support. The valueString will be (1..1). The slices were removed from patientidentifier and medicalrecordnumber and patientaccountnumber were added to the supportingInfo slice discriminator.

       

      Show
      Two new supportingInfo slices for IP, OP, and Professional EOB will be defined for medicalrecordnumber and patientaccountnumber.  We will create two new slices with a cardinality of (0..1) and marked as Must Support. The valueString will be (1..1). The slices were removed from patientidentifier and medicalrecordnumber and patientaccountnumber were added to the supportingInfo slice discriminator.  
    • Resolution Vote:
      Mark Roberts/Laurie Burckhardt: 16-0-1
    • Change Category:
      Enhancement
    • Change Impact:
      Compatible, substantive
    • Pre Applied:
      Yes
    • Applied for Version:
      1.1.0

      Description

      Two patient identifiers defined as Must Support in the Patient resource , MedRecNum & PatAcctNum, are assigned by providers.  These identifiers are unique for each member for a specific claim.

      The values change every time a new claim is created for a member and cause implementers to update Patient data every time a claim is received.   It seems this data does not truly serve the purpose as a patient identifier.  

      Implementers requested guidance.  view it in Zulip.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              taylorpatriciab Patricia Taylor
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:
                Vote Date: