WHO-UMC IDMP Management and Publish API, published by Uppsala Monitoring Centre. This guide is not an authorized publication; it is the continuous build for version 0.1.0 built by the FHIR (HL7® FHIR® Standard) CI Build. This version is based on the current content of https://github.com/Uppsala-Monitoring-Centre/WHO-UMC-IDMP-Service/ and changes regularly. See the Directory of published versions

Change management

This part of the specification is only on a DRAFT level, it is not yet decided how the change management will be done but ucrrently FHIR subscriptions is the planned way forward.

Introduction

Updates can happen to resources for many different reasons like an update of information within the resource or a status change. It could be a completed Task, a retired/replaced SubstanceDefinition GSID and so forth. What they have in common is the need to inform other parties about the change to allow them to act on the change if needed.

Client updating a resource (requesting an updated/new ID)

Any changes to resources sent to the IDMP Service as requests (Tasks) by clients should be notified to the Service using a new Task in the same way as the original request.

Resource updated by the maintenance organization

Changes to resources within the IDMP Service are notified using FHIR subscriptions. TBD.