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

add HIPAA consideration for unsolicited service determination

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: Medium Medium
    • US Da Vinci CRD (FHIR)
    • 1.1.0-ballot [deprecated]
    • Financial Mgmt
    • Supported Hooks
    • Hide

      Both CRD and DTR will provide the ability for a payer that has sufficient information to determine that a service, item, referral, or appointment that normally requires prior authorization does not need it in this instance (based on information held by the payer, sent by the provider as part of CRD, or retrieved from the patients record).  The payer SHALL return a specific coverage code (to indicate the item is covered and PA submission is not required) as part of the coverage extension and a unique ID that SHALL be included in the X12 837 K3 segment for the associated claim.  This code and unique ID provide evidence of the payer's determination to not required prior authorization for the associated service, item, referral, or appointment.

      Show
      Both CRD and DTR will provide the ability for a payer that has sufficient information to determine that a service, item, referral, or appointment that normally requires prior authorization does not need it in this instance (based on information held by the payer, sent by the provider as part of CRD, or retrieved from the patients record).  The payer SHALL return a specific coverage code (to indicate the item is covered and PA submission is not required) as part of the coverage extension and a unique ID that SHALL be included in the X12 837 K3 segment for the associated claim.  This code and unique ID provide evidence of the payer's determination to not required prior authorization for the associated service, item, referral, or appointment.
    • Bob Dieterle / Andy Stechischin : 8-0-1
    • Enhancement
    • Non-compatible

    Description

      Bob recently heard from CMS that they expect a CRD/DTR service determination / pre-emptive prior auth to be built with a 278 response for HIPAA compliance (opposite of what we were hoping in https://chat.fhir.org/#narrow/stream/179283-Da-Vinci/topic/pre-emptive.20prior.20auth.20and.20hipaa ). 

       

      We should update the guidance under unsolicited determination to mention something like "Similar to PAS, to use an unsolicited determination there is an expectation that either it has been translated from a 278 response or is being done under a HIPAA exception ( https://build.fhir.org/ig/HL7/davinci-pas/specification.html#processing-prior-authorization-submissions-under-the-cms-exception )"

      Attachments

        Activity

          People

            Unassigned Unassigned
            kjohnsen Kyle Johnsen
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: