FHIR Bridge - Diagnostic Report & MedicationStatement

Implementation
1

Hi,

I have been testing in the last time working of FHIR Bridge using a attached Postman collection and I’ve encountered some issues with 2 requests - Post DiagnosticReport and MedicationStatement. When trying to send DiagnosticReport there is:

An error has occurred: Coding must have a display or TerminologyService must not be null

With MedicationStatement:

{"error":"Unprocessable Entity","message":"/content[openEHR-EHR-OBSERVATION.medication_statement.v0, 1]/data: Attribute data of class OBSERVATION does not match existence 1..1"}

The requests are as they were in the collection and I did not changed anything. Did anything changes in working of FHIR Bridge for those objects?

Thank you

2

  1. You need a terminologyService for that example as explained.

  2. maybe that request is just old and the validation of ehrbase is more rigid now compared to back then.

3

Thanks Severin. I resolved the first issue with terminologyService, however still no idea with second one. Isn’t the validation of request connected with the OPT template that FHIR Bridge contains?

4

The second error is saying that the mandatory data tree in the medication statement is not being populated. Can you post a sample of the original fhir bundle?

5

Sure, this is the fhir bundle that I am trying to send:

{
    "resourceType": "MedicationStatement",
    "meta": {
        "profile": [
            "https://www.netzwerk-universitaetsmedizin.de/fhir/StructureDefinition/pharmacological-therapy"
        ]
    },
    "status": "active",
    "medicationCodeableConcept": {
        "coding": [
            {
                "system": "http://snomed.info/sct",
                "code": "413591007",
                "display": "Product containing atazanavir (medicinal product)"
            },
            {
                "system": "http://fhir.de/CodeSystem/dimdi/atc",
                "code": "J05AE08",
                "display": "Atazanavir"
            }
        ],
        "text": "Atazanavir"
    },
    "subject": {
        "reference": "/Patient?identifier=urn:ietf:rfc:4122|{{patientId}}",
        "identifier": {
            "system": "urn:ietf:rfc:4122",
            "value": "{{patientId}}"
        }
    },
    "effectiveDateTime": "2020-10-19T08:43:33+02:00"
}
6

Thanks - nothing unusual to see there. Can you share the target .opt? THere was no collection attached that I can see.

7

This is the opt file (this he above bundle is sample request from FHIR Bridge):
GECCO_Medikation.opt (205.4 KB)