TIMS content deployment

timsbiomed / issues

TIMS issue tracker.

1 stars 0 forks source link

Open ShahimEssaid opened 1 year ago

ShahimEssaid commented 1 year ago

To describe our content deployment approach.

ShahimEssaid commented 1 year ago

For TIMS FHIR content:

Minimal requirements:

Build and release proper FHIR NPM packages to be used by various FHIR tooling. See the following for what a FHIR package is: https://confluence.hl7.org/display/FHIR/NPM+Package+Specification
Deposit these packages at URLs so they can be retrieved with a simple GET request.

Later requirements:

Send a POST request (with needed parameters) to our HAPI instance(s) whenever a new package is available so consumers (our own HAPI instances) can download and use as needed.
At a later point we can think about integrating these packages into the FHIR registry, or build our own registry if needed. See: https://confluence.hl7.org/display/FHIR/FHIR+Package+Registry+User+Documentation

joeflack4 commented 1 year ago

We discussed variations of repository setups where we could put release artefacts.

Currently, we have:

I think we're going to go with one of these two setups instead though: a.