Introduction

The capability statement below describes the FHIR resources, profiles, operations, and search parameters that the eOrders FHIR server supports. Use this as a reference when implementing a placer, filler, or patient-portal integration to understand what interactions are available and which are mandatory (SHALL) vs. recommended (SHOULD).

Genie Solutions eOrders Capability Statement

• Implementation Guide Version: 1.3.2
• FHIR Version: 4.0.1
• Supported Formats: json, xml
• Published on: 2026-09-30
• Published by: Magentus Practice Management

Note to Implementers: FHIR Capabilities

Any FHIR capability may be 'allowed' by the system unless explicitly marked as 'SHALL NOT'. A few items are marked as MAY in the Implementation Guide to highlight their potential relevance to the use case.

FHIR RESTful Capabilities

Capabilities by Resource/Profile

Summary

The summary table lists the resources that are part of this configuration, and for each resource it lists:

• The relevant profiles (if any)
• The interactions supported by each resource (Read, Search, Update, and Create, are always shown, while VRead, Patch, Delete, History on Instance, or History on Type are only present if at least one of the resources has support for them.
• The required, recommended, and some optional search parameters (if any).
• The linked resources enabled for _include
• The other resources enabled for _revinclude
• The operations on the resource (if any)