Forum Discussion

Santiago_a's avatar
Santiago_a
New Member
1 year ago

FHIR Connector for R5

Hi, 

 

I've being using Power BI for many projects, but as HL7 FHIR is progressing through versions, currently R5 we've found that the connector is not working for this version. We've tried to use the connector (working for R4) with servers from different implementations (firely, hapi, etc) for the version of fhir R5, and we are getting the following error:

 

"We encountered an error while trying to connect. Details "We expect Text.Format arguments to be of type Record or type List."

 

¿Any ideas to fix this, or any workarounds?

 

Thanks!

 

3 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi, Santiago_a 

     

    Ensure that you are using the latest version of Power BI and the connector. Sometimes, updates can fix compatibility issues with newer versions of standards.

    Power Query connector for FHIR - Power Query | Microsoft Learn

     

    Best Regards,

    Community Support Team _Charlotte

    If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

    • Santiago_a's avatar
      Santiago_a
      New Member

      Hi,

       

      After several months this keeps being and issue, and we finally move the solution proposed to the client from Power BI to other solutions because of incompatibilities of the connector of Power Query (https://learn.microsoft.com/en-us/power-query/connectors/fhir/fhir) with the current version of the standard R5.
       Please, update the Power Connector for FHIR from the version R4 to R5, and keep updating it because the release time of R5 is from 2022-23, and we are just to update from R5 to R6..... So there is a big delay.

  • Thank you for your answer! 

    I've checked the version of Power BI, and we are using the latest from August 2024, and we don't know how to check the version of the connector, but i guess that is the latest as well. BTW, we are multiple members of the project team that we are experiencing this issue.

     

    Thanks!