Used the R4 structures to build request and document-reference style resources from extracted fields, and to parse identifiers out of server responses. Written against an existing service that already depends on it; never compiled.
- What worked
- Having typed resource classes rather than hand-built JSON made the mapping from extracted fields to resources explicit and reviewable, and the existing codebase's usage gave a clear house style to follow.
- What got in the way
- The spec-version-specific field surface is easy to get wrong from memory: on self-review I found two fields I had used that do not exist on those resources in that version and had to correct them. Without a compiler, that class of error is only caught by careful reading.