Access
Resources
Admin

MedX Registry

A community-maintained catalogue of medical devices, health software, organizations, facility lists, and LOINC-coded observations. Built for interoperability with FHIR R4 and designed for low-resource health systems.

What's in the registry?

The registry stores six resource types, all modelled on FHIR R4:

Devices
DeviceDefinition
Lab analysers, POC devices, medical equipment with connection and parameter mappings.
Software
DeviceDefinition (app)
EMR, LIS, HMIS, middleware and FHIR server applications with protocol metadata.
Organizations
Organization
Manufacturers, publishers, health authorities and service providers.
Collections
List
Master facility lists, device catalogues, LOINC subsets and protocol compilations.
Locations
Location
Health facilities cross-referenced with MFL IDs and DHIS2 UIDs.
Observations
ObservationDefinition
LOINC-coded observation definitions with reference ranges and device linkages.

Access model

The registry exposes two access tiers:

  • Public read — anyone can query approved records without authentication.
  • Authenticated write / admin — submitting proposals, approving records, and managing private org-scoped data requires a MedX account with the appropriate SMART on FHIR scopes.

Data access uses the Registry Client, a typed SDK for JavaScript/TypeScript. There is no GraphQL endpoint. REST-style admin endpoints are exposed through the same client under an admin namespace and are gated by server-side scope validation.

Suggest an edit —
Your changes become a public proposal for review
This creates a change proposal. Your edit will be publicly visible at /review and applied to the record once approved by a reviewer.
Structured edits are available on device and software records. Open a device or software detail page to suggest catalogue changes.
Change description

You'll be notified when your proposal is reviewed.

Propose parameter mappings —
Maps device local codes to LOINC for interoperability
This creates a change proposal. Mappings appear on the Review page. When approved, they are merged into the device's FHIR ConceptMap (contained).
Mappings to propose
Notes
Upload Automation plugin
Zip archive uploads to storage when you submit; version is assigned automatically
This creates a change proposal. First upload is v1.0.0; each later upload for the same slug increments the major version. The .zip must include README.md (or readme.md) at the root of the archive, named {slug}-v{n}.zip. The .zip stays local until you submit.
Plugin archive (.zip)
📦
Drop .zip here or click to browse
One file only · max 25 MB · uploads when you submit
Plugin identity

Enter a slug to preview the assigned version.

Catalogue targets
Readme
The plugin README is taken from README.md in the uploaded zip root. It can’t be edited here.
Add document
PDF is uploaded to storage only when you submit the proposal
This creates a change proposal. The PDF stays on your device until you submit. Closing the drawer without submitting does not upload anything to storage.
Catalogue target
PDF document
📄
Drop PDF here or click to browse
One file only · uploads when you submit
New organisation
Creates the organisation immediately and grants you "owner" on it.

Lowercase letters, numbers, and hyphens only. This becomes the org's permanent id and its plugin-publishing namespace.

New machine
Submitted for review. It joins the catalogue once an admin approves it.
Machine
Choose a manufacturer

The ID is made from the manufacturer and the name, and can't be changed later. Plugins refer to machines by it.

Connection interfacesAt least one
Catalogue protocolsAt least one
Note to the reviewer
New software
Submitted for review. It joins the catalogue once an admin approves it.
Software
Type a name

The ID is made from the name and can't be changed later. Plugins target software by it.

TypeAt least one
CapabilitiesOptional
Note to the reviewer