Stream: hapi
Topic: process-message
Edward Castagna (Apr 26 2021 at 14:37):
when calling $process-message on a hapi-fhir 5.2.0 server with FHIR 4.0.1 with us core 3.1.1. what validation will be done? Will the built in validation for the $process-message as to deliverability be done? will core 3.1.1 validation be done ? Will any content validation be done which is also loaded up on the server ? will that validation be included in the process-message call or through other calls against the server? (#WeLoveHAPI) @James Agnew
Edward Castagna (May 18 2021 at 22:20):
It's been confirmed by another user that my $process-message doesn't seem to be responding with other than a...
{
"resourceType": "OperationOutcome",
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\"><h1>Operation Outcome</h1><table border=\"0\"><tr><td style=\"font-weight: bold;\">ERROR</td><td>[]</td><td><pre>This operation is not yet implemented on this server</pre></td>\n\t\t\t\t\t\n\t\t\t\t\n\t\t\t</tr>\n\t\t</table>\n\t</div>"
},
"issue": [
{
"severity": "error",
"code": "processing",
"diagnostics": "This operation is not yet implemented on this server"
}
]
}
I'm open to suggestions.
https://fhirconnect.altarum.org/hapi-fhir-jpaserver-medmorph-kitchensink
Edward Castagna (May 19 2021 at 13:46):
Does hapi-fhir jpaserver support Operation "$process-message" out of the box. what additional gears can be included in the environment build to get it to respond that it is implemented. it does respond that it doesn't support a get when getting. https://fhirconnect.altarum.org/hapi-fhir-jpaserver-medmorph/fhir/$process-message doing the get shows
{
"resourceType": "OperationOutcome",
"text": {
"status": "generated",
"div": "<div xmlns=\"http://www.w3.org/1999/xhtml\"><h1>Operation Outcome</h1><table border=\"0\"><tr><td style=\"font-weight: bold;\">ERROR</td><td>[]</td><td><pre>HTTP Method GET is not allowed for this operation. Allowed method(s): POST</pre></td>\n\t\t\t\t\t\n\t\t\t\t\n\t\t\t</tr>\n\t\t</table>\n\t</div>"
},
"issue": [ {
"severity": "error",
"code": "processing",
"diagnostics": "HTTP Method GET is not allowed for this operation. Allowed method(s): POST"
} ]
}
and when putting the default zika post it responds with
the operation operation not yet implemented on this server.
next steps?
Kevin Mayfield (May 19 2021 at 14:31):
I've always coded this.
How the FHIR Message is going to be processed is down to receiving system, not sending system.
For example do you update your own resource with a received Patient resource, use the copy you already have, create a new Patient, etc.
I don't think this can be out of the box behaviour.
Edward Castagna (May 19 2021 at 15:18):
@Kevin Mayfield so given that hapi-fhir-jpaserver doesn't have the $process-message operation as an out of the box behavior which is defined by the developer ( for instance medmorph ). adding it to the jpaserver might have a couple of levels of supporting the operation. adding some code to the server, adding some api using the code to the server, exercising the code... when it responds that operation not yet implemented on this server does that mean that $process-message is not supported on the server or a specific message-type is not implemented... is there a different way of building a jpaserver so that it's a messaging fhir server than building it to be a restful fhir server?
Kevin Mayfield (May 20 2021 at 06:41):
I wouldn't put it on the jpaserver, I've always created a seperate HAPI restful server to do this.
Last updated: Apr 12 2022 at 19:14 UTC
