Skip to content
This repository has been archived by the owner on Apr 18, 2024. It is now read-only.

Test payload with AdverseEvent doesn't match with FHIR 3.0.1 #289

Open
Rende11 opened this issue Jan 15, 2019 · 2 comments
Open

Test payload with AdverseEvent doesn't match with FHIR 3.0.1 #289

Rende11 opened this issue Jan 15, 2019 · 2 comments

Comments

@Rende11
Copy link

Rende11 commented Jan 15, 2019

Test:
ClinicalResources/Resource Test Adverse Event/AdverseEvent: Create New

Received:

{
"resourceType": "OperationOutcome",
"issue": [
{
"severity": "error",
"code": "invalid",
"diagnostics": "{:path [:suspectEntity 0 :causality], :message "expected type of string"}"
},
{
"severity": "error",
"code": "invalid",
"diagnostics": "{:path [:event], :message "extra property"}"
},
{
"severity": "error",
"code": "invalid",
"diagnostics": "{:path [:kind], :message "extra property"}"
},
{
"severity": "error",
"code": "invalid",
"diagnostics": "{:path [:severity], :message "extra property"}"
},
{
"severity": "error",
"code": "invalid",
"diagnostics": "{:path [:resultingCondition], :message "extra property"}"
}
]
}

@pcosmog
Copy link

pcosmog commented Apr 1, 2019

+1 - I'm running into this issue as well

@pcosmog
Copy link

pcosmog commented Jun 24, 2019

Note also that the "Search Test Adverse Event" test for STU3 is outputting the error msg "The server does not support the following params: event, kind, resultingcondition, severity."

None of these are STU3 fields; "event, resultingcondition, severity" are all R4.

"Kind" isn't even R4, not sure where it comes from ??

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants