Totals and Details Responses


The FHIR Response for Totals and Details have been updated to remove some of the restrictions that exist today. Though structurally different than CPHA3, these transactions fulfil the existing business requirements in a modernized fashion. While mapping may be achievable to the existing CPHA3 functionality, it is significantly more beneficial to the Pharmacy to natively support the new FHIR queries in order to take advantage of the streamlined functionaliy and the flexibility that it offers. Adjudicators will need to support new FHIR queries while continuing support for CPHA queries for a period of time, and it may be more desirable to support FHIR natively, rather than to support mapping between the two message standards.

Totals Response

The Totals Response, "daily-totals-OUT" will return the Totals, based on the criteria that has been specified in the request.

The FHIR MH.event type will be CPHA transaction type 31 for for the Totals response. CPHA transaction types 32 and 33 will be deprecated.

DISCUSISON REQUIRED ON THE FOLLOWING ITEMS

  • Current design allows for totals to be returned a) ALL b) by carrier c) by carrier/group d) all of the above. Need to determine what level of breakdown is required by carrier/group.

  • Review data elements to see if it is too detailed, or if anything is missing. eg do you need both the number of transactions and the amount for pay cardholder? Do you need reversal counts and amounts by carrier/group?

  • Today, the provider will initiate as many requests in order to deliver the detailed records desired during a specified adjudication date. This will be eliminated as it will be handled in a single request

  • In the Details response- Current prescription numbers that are identical may occur more than once during an adjudication date (e.g. a claim is resubmitted following a reversal or rejection). This creates a possibility that the prescription number which appears more than once during an adjudication date occurs at an interval of 14 records.

  • In response to a request for detailed records, the processor will return Fields E.01.03 through E.06.03 plus the number of detail records (Field H.65.03) followed by up to 14 repetitions of Current Rx Number (H.66.03) and Amount Payable/ Reversed (H.67.03).

.

  • See mappings for further details

New Functionality in FHIR

  • FHIR transactions are streamlined to a single response for totals (transaction 31). The response will include transaction counts/totals for each day requested within the requested time period. Daily totals will be broken down by pay patient and pay providers and will also include reversal counts.
  • Details will comply with the time period specified in the request, which may be beyond a single day.
  • The response will comply with the "results rule" to indicate whether the carriers and/or groups specified in the request will be "included" or "excluded". If there are no carrier/groups specified, the default is to include details for all.
  • 14 Day Restriction will only be applied if indicated in the request. This will be used for backward compatibility only.
  • The 14 record restriction (packets of 13) on the result set does not apply unless indicated. While the time period is not restricted in FHIR, the maximum recommended period is 31 days which all adjudicators should support. Each implementer will communicate their supported time period.
  • FHIR paging mechanism. Refer to Discussion re Daily Totals and Details Request

Details Response

The Details Response, will return the Adjudication Details as specified in the request message.

The FHIR MH.event type will be CPHA transaction type 81 for for the Details response. CPHA transaciton types 82 and 83 will be depreacted as the Details will natively include this data.

New Functionality in FHIR

  • FHIR transactions are streamlined to support a single response for details (transaction 81). The response will include transaction counts/totals for each day requested within the requested time period. Daily totals will be broken down by pay patient and pay providers and will also include reversal counts.
  • Details will comply with the time period specified in the request, which may be beyond a single day.
  • The response details will comply with the "results rule" to indicate whether the carriers and/or groups specified in the request will be "included" or "excluded". If there are no carrier/groups specified, the default is to include details for all.
  • 14 Record Restriction will be applied as per the request
  • The 14 record restriciton (packets of 13) on the result set does not apply unless indicated. While the time period is open ended in FHIR, the maximum recommended period is 31 days which all adjudicators should support. Each implementer will communicate their supported time period.
  • FHIR paging mechanism. Refer to Discussion re Daily Totals and Details.