This page is part of the Magentus Practice Management FHIR Implementation Guide (v1.3.2: Releases Draft) based on FHIR (HL7® FHIR® Standard) R4. No current official version has been published yet. For a full list of available versions, see the Directory of published versions

Request Register

The request register is an internal FHIR repository where diagnostic requests are stored prior to being taken up by a diagnostic service, either through directed assignment or patient choice.

Profiles

Magentus Profile	Abstract	FHIR® Resource	Purpose
EOrders Registry Provenance	Yes	Provenance	Abstract base — tracks allocation of an eOrder Bundle to a filler
EOrders Registry Transfer Provenance	No	Provenance	Records directed assignment of an order to a filler via Task.owner
EOrders Registry Claim Provenance	No	Provenance	Records a patient-initiated claim of an order by an alternate filler

When to use each Provenance type

Transfer Provenance is recorded when an order is submitted with a designated filler — i.e., when one or more fulfillment Tasks carry a Task.owner. The agent[primary-filler] slot identifies the originally designated organisation.

Claim Provenance is recorded when a filler claims an existing order via the $claim operation. In this case the original fulfillment Task is cancelled and a new Task set is created for the claiming organisation. The agent[primary-filler] slot identifies the original filler (if known) and agent[alternate-filler] identifies the claiming organisation.

Both profiles target the submitted order Bundle via Provenance.target.

Note that neither the original filler nor the alternate filler can determine the identity of the other party — privacy of each filler's involvement is maintained by the registry.