Closed thomasyu888 closed 3 years ago
Yes, I need to have another pass at how objects reference other objects. Thanks for highlighting this.
The PR mentioned above is actually not linked to this issue.
There seem to be different standards within this API.
It's actually the case: there is the design adopted for the general API that is inspired from Google API, and the FHIR standard used to store resources in FHIR stores. For example, schemas freely defined as part of the Google API have often a property name
. However, the FHIR Patient schema already have a property name
that conflicts with Google's property name
.
FHIR Patient schema found in Google's doc:
{
"birthDate": "1970-01-01",
"gender": "female",
"id": "PATIENT_ID",
"meta": {
"lastUpdated": "2020-01-01T00:00:00+00:00",
"versionId": "VERSION_ID"
},
"name": [
{
"family": "Smith",
"given": [
"Darcy"
],
"use": "official"
}
],
"resourceType": "Patient"
}
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
All the other rest calls return name, just like getting annotations:
This becomes more complex when I'm writing code to get a clinical note in the client. We would have:
There seem to be different standards within this API.