MPPS integration

Xenrad accepts MPPS session updates over HTTPS so modalities and PACS bridges can report procedure-step state for a site. Authentication is the same site-scoped API key used by FHIR and HL7 HTTP. The MPPS host is separate from those other surfaces.

MPPS HTTP host — https://mpps.stg.xenrad.io (POST https://mpps.stg.xenrad.io/ingest with X-API-Key).

Request shape

POST /ingest on the MPPS HTTP host with X-API-Key: <api_key> and a JSON body.

You must send sop_instance_uid for the MPPS object, study_uid for the Study Instance UID the session belongs to, and status such as IN PROGRESS or COMPLETED. You may send attributes as an object when you need extra fields. Do not send site_id in the body. The service resolves the site from the API key.

Example

curl -sS -X POST \
  -H "X-API-Key: $XENRAD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "sop_instance_uid": "1.2.3.4.5",
    "study_uid": "1.2.3.4.6",
    "status": "COMPLETED",
    "attributes": {}
  }' \
  "$MPPS_BASE/ingest"

On success the service returns JSON with success: true and a session_id UUID. On validation or persistence failure you get success: false and an error string.

Interactive reference

When enabled for your environment, open /api/documentation on the MPPS host. OpenAPI is at /api/documentation/openapi.json.

Where this sits

API keys create and rotate the credential. Endpoints reference tells you which host to call. FHIR can read patient and study context after ingest. HL7 handles demographics and clinical events on its own host. Imaging still arrives through DICOM.