Closed dbooth-boston closed 1 year ago
I added the R5 label because some of these items are relevant to R5.
Relevant to the "union types" sub-issue, here's an example of how to handle union types in JSON-LD: https://tinyurl.com/2p88swzd
http://build.fhir.org/datatypes.html#dateTime
The problem of union types was described in issue #78
Done in R5
We might want to break this into separate issues, but I thought I would experiment with github's new-ish checklist feature.
These are known issues that we'll need to address in a JSON preprocessor. Please add to these if you think of more.
id
elements that get removed by@id
conversion to URIs. This is needed because when the FHIR/JSON says"id": "abc123"
is an@id
in the@context
, it becomes the URI of the element, which means that the "id" string property is lost. Preprocessing can replicate the property to enable it to both stay as a string and become a URI.