Stream: tooling
Topic: Synthea data issue: duplicate identical Locations?
Carl Anderson (Sep 23 2020 at 14:43):
Rather than piling on the other Synthea stream, I'm starting a new one for a separate data issue.
First, some background. I generated about 1,000 patients a while back to load them into a HAPI server for a connectathon scenario. I selected a handful of patients from the 1,000 to load at first, and ran into some issues right away with duplicate, identical resources being created for each patient due to the way I was loading the data - there was no flaw in the Synthea data itself.
I've resolved those duplicate identical resources issues by using conditional references and re-ordering the resources in the batch slightly to load all resources before they are referenced elsewhere. This works fine.
The latest problem appears to be in the Synthea data itself. I've found several Location resources which are identical across patients, but who have different id values. I have not found other resource types yet that follow this pattern - it appears to be an issue with Locations (although I haven't checked everything else).
abbie.location
{
"fullUrl": "urn:uuid:5f0a03d6-92b8-6ec2-cdd2-893281c43776",
"resource": {
"resourceType": "Location",
"id": "5f0a03d6-92b8-6ec2-cdd2-893281c43776",
"meta": {
"profile": [
"http://hl7.org/fhir/us/core/StructureDefinition/us-core-location"
]
},
"status": "active",
"name": "UNITYPOINT HEALTH - MERITER",
"telecom": [
{
"system": "phone",
"value": "6084176000"
}
],
"address": {
"line": [
"202 S PARK ST"
],
"city": "MADISON",
"state": "WI",
"postalCode": "53715",
"country": "US"
},
"position": {
"longitude": -89.430121,
"latitude": 43.087806
},
"managingOrganization": {
"reference": "urn:uuid:e6c5d179-370a-3659-9ce6-3d09da3c3ad0",
"display": "UNITYPOINT HEALTH - MERITER"
}
},
"request": {
"method": "POST",
"url": "Location"
}
}
adolfo.location
{
"fullUrl": "urn:uuid:47ba9ed9-92d1-4727-7089-ced1836ea2a9",
"resource": {
"resourceType": "Location",
"id": "47ba9ed9-92d1-4727-7089-ced1836ea2a9",
"meta": {
"profile": [
"http://hl7.org/fhir/us/core/StructureDefinition/us-core-location"
]
},
"status": "active",
"name": "UNITYPOINT HEALTH - MERITER",
"telecom": [
{
"system": "phone",
"value": "6084176000"
}
],
"address": {
"line": [
"202 S PARK ST"
],
"city": "MADISON",
"state": "WI",
"postalCode": "53715",
"country": "US"
},
"position": {
"longitude": -89.430121,
"latitude": 43.087806
},
"managingOrganization": {
"reference": "urn:uuid:e6c5d179-370a-3659-9ce6-3d09da3c3ad0",
"display": "UNITYPOINT HEALTH - MERITER"
}
},
"request": {
"method": "POST",
"url": "Location"
}
}
diff abbie.location adolfo.location
2c2
< "fullUrl": "urn:uuid:5f0a03d6-92b8-6ec2-cdd2-893281c43776",
---
> "fullUrl": "urn:uuid:47ba9ed9-92d1-4727-7089-ced1836ea2a9",
5c5
< "id": "5f0a03d6-92b8-6ec2-cdd2-893281c43776",
---
> "id": "47ba9ed9-92d1-4727-7089-ced1836ea2a9",
Considering that the Organiation.id is constant across locations and patients, shouldn't the Location.id also be constant?
Jason Walonoski (Sep 23 2020 at 16:13):
Yep, looks like a bug.
Jason Walonoski (Sep 23 2020 at 16:15):
Created https://github.com/synthetichealth/synthea/issues/797
Last updated: Apr 12 2022 at 19:14 UTC
