{
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "error",
"code": "processing",
"diagnostics": "Invalid request: The FHIR endpoint on this server does not know how to handle POST operation[Encounter] with parameters [[]]"
}
]
}
I am not sure what the parameter [] is. To setup the JSON, I followed what is in the OpenMRS doc here.
Do you want to track the encounter posting with the streaming pipe line of the analytics engine reading your my-sql binlog for the change in the encounter posted to openmrs
So note that creating an encounter through the FHIR2 API requires you to have the necessary data already setup in your OpenMRS instance, so, for instance, the Visit that this encounter is partOf needs to already exist, the patient the encounter is for needs to exist, the patient needs to exist, the practitioner referenced needs to exist and be a valid OMRS provider, the location of the encounter needs to exist in your instance, as does the encounterType. That’s probably the issue with the first request. (So, in the context where we actually use that sample request for a test, we have the data shown here loaded into the database)…
Ensure you are using fhir2 module version that has support for posting encounters
@gcliff thanks for the help on this, this was my issue! The FHIR module I was using didn’t have the PR you linked to. Using the openmrs/openmrs-reference-application-distro:nightly image helped resolve the issue