Stream: hapi
Topic: SOAP
Jens Villadsen (Mar 26 2020 at 12:41):
I have an exotic case where a customer of mine would like the outer interface to be Web service SOAP based and the interior to be FHIR based. Does anyone have any good input on how to make this as hazzle free as possible? Setting up HAPI FHIR and the endpoints is not the issue. The issue is to make the FHIR model or parts of it as easy mappable to a Java based SOAP infrastructure. I have wondered how much is doable with looking into Document/literal WSDL binding but it is not really 'my thing'/comfort zone
René Spronk (Mar 26 2020 at 15:31):
It depends on what web services they'd like to have (or: are having). Creating create, read, update and delete (and query stored procedure) SOAP-based services would be the easiest mapping of course.
Jens Villadsen (Mar 26 2020 at 20:30):
right ... the setup IS exotic ... and probably too custom to have a sane generalization strategy for
René Spronk (Mar 27 2020 at 07:26):
I think Italy (?) had a similar challenge as Denmark does: the national secure infrastructure is based on SOAP. Obviously FHIR can be used in a services context, as messages, as documents, as a set of services that mimics REST, or as some other collection of (micro)services. The options are wide open. One option would be to re-implement any existing services to use FHIR payloads. If you're designing new services next to old ones, the granularity and style of the new services should probably be aligned with the design philosophy of the old ones to ensure ease of uptake.
Jens Villadsen (Mar 27 2020 at 15:09):
There's no good computable path using SOAP and FHIR in combination. I guess we'll do a custom SOAP endpoint and bridge that for the HAPI backend. Then once the national infrastructure is capable of something else, we can remove that part ...
Last updated: Apr 12 2022 at 19:14 UTC
