⌘K
Sign upSign in
All guides
APEX Nexus· 10 min

Nexus Clinical API Integration

Patients, appointments, medications, imaging, and telehealth via REST and FHIR on APEX Nexus.

  1. 1

    Clinical REST facade

    Nexus exposes enriched REST endpoints for common clinical workflows alongside native FHIR R4. Use FHIR for interoperability; REST facades for portal-optimized payloads.

    bash
    "text">-amber-300 font">-semibold">curl "text-cyan-300">-s "https://api.parkerapex.com/api/patients" \
  "text-cyan-300">-H "Authorization: Bearer YOUR_TOKEN"
  2. 2

    FHIR Patient search

    Search patients by GPID identifier — all patient creation flows through IdentityResolver.

    bash
    "text">-amber-300 font">-semibold">curl "text-cyan-300">-s "https://api.parkerapex.com/fhir/R4/Patient?identifier=https://parkerapex.com/gpid|APX">-EXAMPLE" \
  "text-cyan-300">-H "Authorization: Bearer YOUR_TOKEN" \
  "text-cyan-300">-H "Accept: application/fhir+json"
  3. 3

    Appointments & encounters

    Schedule via FHIR Appointment resources or the appointments module. Encounters link clinical documentation to visits.

  4. 4

    Medications & imaging

    MedicationRequest for e-prescribing; ImagingStudy and DiagnosticReport for DICOM-integrated workflows.

Related