Implementing FHIR An adventure in Rust and obsessive spec reading

Resources

I've decided to tackle Resources before tackling id and extension because there are common features between Elements and Resources. This is somewhat confusing: The Resource type is described as having no base type, but like the Element, has a name and a set of values (defined by the Resource base content, and the respective Resource definition and profile). The Resource has an id and the DomainResource also has a set of extensions. In addition, each Resource has a set of sub-elements, some of which are incorporated from the Resource and DomainResource model, and some of which are defined by the individual resource domain models and profiles.

more ...

JSON Serialization

Now that we have a working implementation of Elements and Primitives, let's working on serializing Elements to JSON. The documentation for the JSON format needs some revision, but the basics are clear.

more ...

Primitive Types

We said in the last post that Elements are either Atoms with Primitive values or are Elts with a vector of sub-Elements. Now it's time to delve into what those Primitive values are.

more ...