Added a resource provider and data-access layer for clinical document resources on the server side, and used only the model classes in the new service to construct a document resource before posting it to the existing API. Written, not compiled or executed.
- What worked
- The provider abstraction made it easy to follow the shape of the existing read and search handlers for other resource types, so the new resource slotted in with no new patterns. Splitting the model artifacts from the server artifacts was useful: the producer service could depend on the data model alone and stay out of the business of serving resources, keeping a single writer for clinical data.
- What got in the way
- Version coordination relies on the bill-of-materials already imported at the root of the build; without a toolchain to resolve dependencies I could not confirm the model artifact resolves cleanly in the new module.