Page tree
Skip to end of metadata
Go to start of metadata


This call is at 2:30 PM ET, 1:30 PM CT, 12:30 PM MT, 11:30 AM PT

Join using: https://leavittpartners.zoom.us/j/461256971Meeting ID: 461 256 971

+16468769923,,,461256971# US
+13126266799,,,461256971# US

Dial by your location:   

+1 646 876 9923
+1 312 626 6799
+1 301 715 8592   

+1 346 248 7799
+1 669 900 6833
+1 253 215 8782 

Meeting ID: 461 256 971


  Agenda Outline

Agenda Item

  • Search Parameters

  • Profile Abstract or Concrete

  • CarinEOB.id Cardinality

  • Increasing Binding Strength to Required

  • Example Binding Strength?






                                                                                                                                                                                                                                                    


Action Items

    • CARIN BB RESTful API
      • Pat to update the search parameters to include the following: If payers have data as of date of service they SHALL include it, otherwise they MAY return data as of current date in the meta.lastUpdated
    • RESTful Capabilities by Resource/Profile
      • Pat to update to provide context to get right reference resource or do not support query via ID
      • Add guidance to explain that an app developer will need to create a custom _include” so that the server does not pick up the wrong information or provide versioned references

Recap

Search Parameters

  • CARIN BB RESTful API
    • The EOB resource is the focal of the CARIN BB Resource
    • Several Reference Resources are defined directly/indirectly form the EOB: Coverage, Patient, Organization (Payer ID), Practitioner, Organization (Facility), PractitionerRole, Location
    • All reference recourses within the EOB will have meta.lastUpdated flagged as must support
    • Payers SHALL provide the last time the data was updated or the date of creation in the payers system of record, whichever comes last
    • Apps will use the meta.lastUpdated values to determine if the reference resources are as of the current date or date of service
    • What point in time is returned?
      • The coverage resource must be returned based on date of service. For the other resources, they can be returned as current date or date of service
    • ACTION ITEMS:
      • Pat to update the search parameters to include the following: If payers have data as of date of service they SHALL include it, otherwise they MAY return data as of current date in the meta.lastUpdated
  • RESTful Capabilities by Resource/Profile
    • To fetch supporting Reference Resources, payers SHALL support _include for all resources referenced by an ExplanationOfBenefit as well as_include=*”, which would bring all referenced resources in the bundle
    • Clients ExplanationOfBenefit searches can use _include=*”, _include” for specific reference resources or no _include” at all (atomic calls) as best suits their use case
    • ACTION ITEMS:
      • Pat to update to provide context to get right reference resource or do not support query via ID
      • Add guidance to explain that an app developer will need to create a custom _include” so that the server does not pick up the wrong information or provide versioned references










  • No labels