# Request Register - Magentus Practice Management FHIR Implementation Guide v1.2.60

* [**Table of Contents**](toc.md)
* **Request Register**

## 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

| | | | |
| :--- | :--- | :--- | :--- |
| [EOrders Registry Provenance](StructureDefinition-eorders-registry-provenance.md) | Yes | [Provenance](https://hl7.org/fhir/R4/provenance.html) | Abstract base — tracks allocation of an eOrder Bundle to a filler |
| [EOrders Registry Transfer Provenance](StructureDefinition-eorders-registry-transfer-provenance.md) | No | [Provenance](https://hl7.org/fhir/R4/provenance.html) | Records directed assignment of an order to a filler via`Task.owner` |
| [EOrders Registry Claim Provenance](StructureDefinition-eorders-registry-claim-provenance.md) | No | [Provenance](https://hl7.org/fhir/R4/provenance.html) | 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](OperationDefinition-EOrderClaimOperation.md). 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.

