Pulling/pushing HL7 from/to a API

To retrieve or send HL7 messages via web APIs, you can create a production that utilizes various InterSystems IRIS components. Here are the relevant steps and considerations:

1. Create a Custom Business Service:
   To periodically send requests to a business process, you can implement a business service using EnsLib.HTTP.GenericOperation. This business service interacts with APIs by sending HTTP requests. The following can be used as a foundation:

   • Configure SSL/TLS settings for secure communication by creating a new SSL configuration if the API requires encrypted communication [1][2][3].
   • Set up headers in your HTTP request, such as the "Authorization" field for specific API requirements. You may use EnsLib.HTTP.OutboundAdapter or %Net.HttpRequest for detailed control over request construction [4][1].

2. Secure TLS Communication:
   To overcome SSL/TLS errors, verify the correct configuration and communication:

   • Create the required SSL/TLS configuration settings, including specifying cipher suites, certificate files, and other attributes. Make sure the chosen configuration matches the API's requirements for compatibility [5][6][4].
   • Test SSL/TLS connectivity via InterSystems tools, such as %Net.HttpRequest. Review the return headers and debugging logs for errors related to SSL errors [3][1].

3. Handling Large and HL7-Specific Messages:

   • Ensure your configuration and object handling supports large HTTP payloads by configuring settings like message content preview limits [2][7].
   • If you need specialized handling for HL7 messages, consider converting them from ER7 to XML or JSON using specific tools that InterSystems provides [8][2][9].

4. Integration with REST APIs:
   Setting up operations for pushing or pulling HL7 messages via REST:

   • Use EnsLib.REST.Operation or %Net.HttpRequest for outgoing REST API calls.
   • Include the relevant authentication, configuration headers, and body formats (e.g., JSON) to meet API specifications.
   • Debug requests using tools like Fiddler or logging configurations [2][1].

5. Common Challenges:

   • Issues with SSL/TLS configurations, improper headers setup, unauthorized HTTP requests, or incorrect payload formatting often lead to errors like TLS protocol mismatches or bad request messages from APIs [3][6].

If you encounter specific error messages or behaviors that remain unresolved, such as "SSL configuration issues with EnsLib.HTTP.GenericOperation," analyze returned debug logs thoroughly and adjust configurations accordingly [7][3][6]. For further reference examples on creating productions or detailed implementations, visit resources provided in InterSystems documentation and GitHub repos [1][2][10][11][5].

Sources:

My instinct is that this <WRITE> error is just indicating that there's some issue with the TLS communication. Can you confirm using another method that the certificate(s) are appropriate?

What is the error from the API when unsecured? Is there a test version of the API you can test without TLS?

By the look of the stack trace, I think the adapter is trying to write request but it fails. Check the SSLConfiguration setting of the operation, it should be the name of an existing, valid, TLS configuration.