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

  • Encounter Data
  • Review of Must Support Data Elements
  • EOB.careteam.provider
  • Profile Abstract or Concrete
  • CarinEOB.id Cardinality
  • Next Week:
  • Increasing Binding Strength to Required
  • Example Binding Strength?






                                                                                                                                                                                                                                                    


Action Items

FHIR-26779 MustSupport elements

  • Need to specify MustSupport contengencies and explain how it will be addressed. Needs to documented.

Patient universal/mastered id work flow

  • This will be taken under advisement by the small group and bring it back to the larger group

FHIR-26629 – EOB.careteam.provider

  • Work with PDex PlaNET group to synergize the usage of the practitioner role profiles during Tuesday’s FM WG call

Recap

FHIR-26779 MustSupport elements

  • The CARIN IG aligns with the MustSupport elements in US Core, so if the server has the data then they are required to expose and supply it. If they do not have the data, then there is a documented way to explain that using a US Core format. If the field is optional, then they can skip it, but must provide an explanation.
  • ACTION ITEM: Need to specify MustSupport contengencies and explain how it will be addressed. Needs to documented.

Patient universal/mastered id work flow

  • Two payers to share information about current active treatment
  • Can also be used to direct information from an old plan to a new plan where it is impractical for the user to authorize an old plans API or Oauth process and instead use the new plan to pull the data.
  • Under the new work flow, the new insurer would send to the old insurer a Member Match. It would include patient, new coverage information, and old coverage as parameters in a bundle.
    • The old insurer would take the unique ID and confirm that they did have that member. Since they could have had that member on more than one insurer with more than one ID, they would use a common identifier to match them.
    • If you don’t find a match or more than one match you would return a 422 – unable to match.
    • If you can match you’d provide a UMB.
    • Update Patient and return parameter bundle.
    • The new insurer query FHIR API for member info and return Member info.
  • ACTION ITEM: This will be taken under advisement by the small group and bring it back to the larger group

 

FHIR-26629 – EOB.careteam.provider

  • Da Vinci is working on this through the PDex PlanNET.
  • ACTION ITEM: Work with PDex PlaNET group to synergize the usage of the practitioner role profiles during Tuesday’s FM WG call

 










  • No labels