Validating resources against a custom FHIR IG

182 views
Skip to first unread message

Olga Patterson

unread,
Dec 8, 2022, 9:32:27 PM12/8/22
to GCP Healthcare Discuss
Hey, all. 
Has anyone tried to deploy US Core or another custom FHIR IG on a GCP FHIR Server? We are trying to do that but get an error that in part reads:
```
412 Precondition Failed
POST https://our_fhir_store/fhir
{
"issue": [
{
 "code": "invariant",
 "details": {
 "text": "in slice \\"race\\": expected field type to match one of: Extension(http://hl7.org/fhir/us/core/StructureDefinition/us-core-race)"
 },
"diagnostics": "in https://<Custom_FHIR_IG>/custom-patient-profile|0.1.0",
"expression": [
        "Bundle.entry[0].resource.ofType(Patient).extension" ],
 "severity": "error"},

```
In patient resource the race extension looks like this:
``` {
"extension": [
{
"url": "ombCategory",
"valueCoding": {
"code": "2028-9",
"display": "Asian",
"system": "urn:oid:2.16.840.1.113883.6.238",
"version": "v1"
}
}
],
},
```
Any idea what exactly is expected in the resource so that it would pass FHIR IG validation? Is there something we need to configure in the FHIR store? Or populate the extension differently?

Thanks!

Mirek Korwel

unread,
Dec 10, 2022, 11:04:35 AM12/10/22
to Olga Patterson, GCP Healthcare Discuss
Hi. 

I'm not sure if that's it, our implementation did accept the patient resource with race slice like in your example; however further validation test had thrown this error: Patient.extension[0]: Extension.extension:text: minimum required = 1, but only found 0 (from http://hl7.org/fhir/us/core/StructureDefinition/us-core-race). In other words, the text extension {"url": "text", "valueString": "Asian"} is the required one. Coding extension may be added (actually, up to 5 of those), but is not required.

I hope that helps. If not, then I have no idea - the coding extension itself looks ok.

Best regards

--
You received this message because you are subscribed to the Google Groups "GCP Healthcare Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gcp-healthcare-di...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gcp-healthcare-discuss/4222b99f-e5e6-41cb-b739-d977124888a6n%40googlegroups.com.


--

Mirosław Korwel

Application Developer

Foothold Technology



This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, notify the sender immediately by return email and delete the message and any attachments from your system.


Nik Klassen

unread,
Dec 12, 2022, 12:10:28 PM12/12/22
to Mirek Korwel, Olga Patterson, GCP Healthcare Discuss
It looks like Mirek is right, the us-core-race extension requires a "text" extension on the extension. There's also an example in the spec http://hl7.org/fhir/us/core/STU5.0.1/Patient-example.json.html

Olga Patterson

unread,
Dec 12, 2022, 4:31:26 PM12/12/22
to Nik Klassen, Mirek Korwel, GCP Healthcare Discuss
Thank you very much. I will test it out.

Olga Patterson

unread,
Dec 12, 2022, 9:43:19 PM12/12/22
to Nik Klassen, Mirek Korwel, GCP Healthcare Discuss
Thank you very much - you were absolutely right. We were missing the value for text. I knew it was something simple like that but I just could not see it until you pointed it out.
Thank you!

On Mon, Dec 12, 2022 at 10:10 AM Nik Klassen <nikkl...@google.com> wrote:

Mirek Korwel

unread,
Dec 13, 2022, 10:04:27 AM12/13/22
to opatt...@verily.com, Nik Klassen, GCP Healthcare Discuss
You're welcome! 
Reply all
Reply to author
Forward
0 new messages