New post
Question
· Feb 7

Transforming a FHIR Response to SDA – Handling Task Resource

#API #FHIR #JSON #REST API #XML #Caché #Ensemble #HealthShare #InterSystems IRIS for Health

I have a scenario where I send a GET request to a broker and receive a FHIR response. When I attempted to use the built-in InterSystems functions to convert this FHIR response into SDA, the transformation failed—likely because it is not a standard FHIR request.

How should I handle this situation? Is there a recommended approach to processing FHIR responses in this context?

Additionally, if I manage to convert the FHIR response into a request format, I noticed that the broker sends a Task resource. However, when I tried to transform it into SDA using the built-in functions, it wasn’t processed successfully.

After checking the ^HS.XF.Transform global, I couldn’t find any predefined DTLs related to the Task resource. This raises a few questions:

  • Does this mean I need to create a new DTL specifically to transform the Task FHIR resource into SDA?
  • If so, do I also need to manually define the source and destination and update the global to register this transformation?

I’d appreciate any guidance or best practices on the best approach to handle this. Thanks in advance!

Product version: IRIS 2023.3
Discussion (3)1
Log in or sign up to continue
Ashok Kumar · Feb 7

Hello @Ali Chaib

I could find the relevant SDA class resource  HS.SDA3.Task for the FHIR Task. AFAMA, there is no built in DTL or relevant FHIR model class available to transfer SDA to FHIR resource. for now, You can create a your own FHIR model class for Task and create a customized DTL under HS.Local.FHIR.DTL. package use the SDA3.Task as destination class for transformation.

0 0
Ali Chaib · Feb 10

Thank you so much @Ashok Kumar 

According to the documentation, the recommended strategy for customizing a DTL transformation (used for converting SDA to FHIR and vice versa) is to:

  1. Create a copy of the standard DTL, and
  2. Modify it.

Once a custom DTL package is specified, the transformation automatically selects the custom DTL instead of the default one.

This approach does not cover a strategy of creating a new DTL from scratch.

And let's say I decided to try it, I have a few questions:

  1. After creating a custom DTL, how do I access it within the transformation logic?
    • I understand that we have the function GetDTL(), which calls a global ^HS.XF.Transform to retrieve the appropriate transformation.
  2. Should I manually add my custom DTL to the built-in global (^HS.XF.Transform) to ensure it's selected correctly?
  3. Is there any official documentation that covers this specific part—such as modifying the global, necessary configuration steps, or best practices—to avoid missing anything critical?
1 0
Ashok Kumar · Feb 10

Hello @Ali Chaib

  1. You need to create you're custom DTL under "HS.Local.FHIR.DTL"  
  2. Once DTL is created. Execute set status = ##class(HS.FHIR.DTL.Util.API.ExecDefinition).SetCustomDTLPackage("HS.Local.FHIR.DTL")  this and this will configure the customize DTL entry in the  ^HS.XF.Config global it's responsible for execute your DTL
  3. Here is the documentation which covers most customization.
  4. As I mentioned earlier, You need to the additional properties in respective SDA extension class.
0 0