slug: nexhealth provider: NexHealth generated_by: planning/capability-mapping/scripts/classify_capabilities.py model: claude-opus-5 frame: - Healthcare Providers min_confidence: 0.7 capability_model: source: https://github.com/vincentmakes/turbo-ea-capabilities license: CC-BY-4.0 attribution: Turbo EA Capabilities by Vincent Verdet — Turbo EA, https://github.com/vincentmakes/turbo-ea-capabilities, CC BY 4.0 notice: NOTICE edge_count: 17 edges: - tag: Appointments spec_file: nexhealth-appointments-api-openapi.yml capability_id: BC-2800.10 capability_id_l1: BC-2800 capability_name: Scheduling & Appointment Management confidence: 0.92 evidence: POST /appointments postAppointments Create appointment" and "API_V2_Entities_Appointment_OnlineBookingDetail reason: Direct create/read/edit of patient appointments including online-booking detail against providers and patients in EHR systems. This is appointment booking for a healthcare provider — Scheduling & Appointment Management. - tag: Available Slots spec_file: nexhealth-available-slots-api-openapi.yml capability_id: BC-2800.10 capability_id_l1: BC-2800 capability_name: Scheduling & Appointment Management confidence: 0.9 evidence: GET /available_slots getAvailableSlots View available slots; schema API_V20240412_Entities_AvailableSlot reason: Exposes bookable appointment availability from practice management systems, which is appointment/provider scheduling. - tag: Clinical Notes spec_file: nexhealth-clinical-notes-api-openapi.yml capability_id: BC-2830.10 capability_id_l1: BC-2830 capability_name: Clinical Note Documentation confidence: 0.9 evidence: GET /clinical_notes getClinicalNotes View clinical notes; schema API_V20240412_Entities_ClinicalNote reason: Reads clinician-authored clinical notes from the EHR, i.e. clinical note documentation. - tag: Appointment Types spec_file: nexhealth-appointment-types-api-openapi.yml capability_id: BC-2800.10 capability_id_l1: BC-2800 capability_name: Scheduling & Appointment Management confidence: 0.83 evidence: POST /appointment_types postAppointmentTypes Create an appointment type" and "API_V2_Entities_AppointmentTypeWithResources reason: CRUD over appointment types with associated bookable resources is the configuration layer of provider scheduling in an EHR/practice-management context, squarely Scheduling & Appointment Management. Slightly below 0.9 because these are configuration objects rather than the booking transaction itself. - tag: Adjustments spec_file: nexhealth-adjustments-api-openapi.yml capability_id: BC-2870 capability_id_l1: BC-2870 capability_name: Healthcare Revenue Cycle Management confidence: 0.8 evidence: POST /adjustments postAdjustments Create adjustment" with schemas "API_V20240412_Entities_Ledger_Adjustment", "API_V2_Entities_Ledger_Insurance_ClaimBasic", "API_V2_Entities_Patient_Ledger_Charge reason: Creating and reading ledger adjustments tied to patient charges and insurance claims is provider revenue-cycle accounting. The evidence is clearly BC-2870, but adjustments straddle payer remittance posting/reconciliation and patient financial services, so no L2 is asserted. - tag: Claims spec_file: nexhealth-claims-api-openapi.yml capability_id: BC-2870.30 capability_id_l1: BC-2870 capability_name: Claim Production & Submission confidence: 0.8 evidence: GET /claims View claims; schema API_V20240412_Entities_Ledger_Insurance_Claim reason: Insurance claim records with charge totals and payouts — provider claim production/status tracking within revenue cycle. - tag: Patients spec_file: nexhealth-patients-api-openapi.yml capability_id: BC-2800.20 capability_id_l1: BC-2800 capability_name: Patient Registration Management confidence: 0.78 evidence: POST /patients 'Create patient'; schemas API_V2_Entities_PatientAddress, API_V2_Entities_PrivacyAuthorization, API_V20240412_Entities_PatientDetailed reason: Creating and reading patient records with demographics, addresses and privacy authorisation is capture and stewardship of registration data for a patient. - tag: Balances spec_file: nexhealth-balances-api-openapi.yml capability_id: BC-2870 capability_id_l1: BC-2870 capability_name: Healthcare Revenue Cycle Management confidence: 0.75 evidence: GET /guarantor_balances View guarantor balances; GET /insurance_balances View insurance balances; schema API_V20240412_Entities_Ledger_GuarantorBalance reason: Patient-accounting ledger balances split between guarantor (patient) responsibility and insurance receivable — provider revenue cycle. Spans patient financial services and payer reconciliation, so L1 only. - tag: Charges spec_file: nexhealth-charges-api-openapi.yml capability_id: BC-2870.10 capability_id_l1: BC-2870 capability_name: Charge Capture & Chargemaster Management confidence: 0.75 evidence: GET /charges View charges; schemas API_V20240412_Entities_Ledger_Charge, API_V20240412_Entities_Procedure, API_V20240412_Entities_FeeScheduleProcedureCode reason: Ledger charges tied to procedures and fee-schedule codes represent clinical charge capture in the provider revenue cycle. - tag: Payment Plans spec_file: nexhealth-payment-plans-api-openapi.yml capability_id: BC-2870.60 capability_id_l1: BC-2870 capability_name: Patient Financial Services confidence: 0.75 evidence: GET /payment_plans 'View payment plans'; schemas API_V2_Entities_PaymentPlanDetailed with API_V2_Entities_PatientBasic reason: Payment plans tied to a patient are patient billing/collections instruments within provider revenue cycle, matching Patient Financial Services. - tag: Working Hours spec_file: nexhealth-working-hours-api-openapi.yml capability_id: BC-2800.10 capability_id_l1: BC-2800 capability_name: Scheduling & Appointment Management confidence: 0.75 evidence: POST /working_hours postWorkingHours Create working hour; GET /working_hour_labels; schema API_V2_Entities_AppointmentTypeBasic reason: Working hours define provider/location availability windows tied to appointment types — the availability layer of provider and resource scheduling in a practice management system, i.e. Scheduling & Appointment Management. - tag: Fee Schedules spec_file: nexhealth-fee-schedules-api-openapi.yml capability_id: BC-2870 capability_id_l1: BC-2870 capability_name: Healthcare Revenue Cycle Management confidence: 0.7 evidence: GET /fee_schedule_procedures View fee schedule procedures; schemas API_V20240412_Entities_FeeSchedule, API_V2_Entities_Price reason: Fee schedules with per-procedure prices underpin provider pricing/reimbursement in revenue cycle; evidence does not cleanly separate chargemaster stewardship from payer contract modelling, so L1 only. - tag: Insurance spec_file: nexhealth-insurance-api-openapi.yml capability_id: BC-2800.30 capability_id_l1: BC-2800 capability_name: Eligibility & Benefits Verification confidence: 0.7 evidence: GET /insurance_coverages View insurance coverages; schemas API_V20240412_Entities_Insurance_PatientCoverageDetailed, API_V2_Entities_Insurance_Subscriber reason: Exposes patient insurance plans and coverage/subscriber details used to establish benefits and coverage before service; verification-adjacent, hence moderate confidence. - tag: Operatories spec_file: nexhealth-operatories-api-openapi.yml capability_id: BC-2800.10 capability_id_l1: BC-2800 capability_name: Scheduling & Appointment Management confidence: 0.7 evidence: GET /operatories getOperatories View operatories; schemas API_V2_Entities_OperatoryWithResources, API_V2_Entities_AppointmentTypeBasic reason: Operatories are the treatment rooms/chairs used as bookable resources, returned with their resources and appointment types — resource scheduling data underpinning appointment booking. recovered_from: healthcare-vertical-edges.json - tag: Payments spec_file: nexhealth-payments-api-openapi.yml capability_id: BC-200.30 capability_id_l1: BC-200 capability_name: Accounts Receivable Management confidence: 0.7 evidence: POST /payments Create payment; API_V2_Entities_Patient_Ledger_Charge, API_V2_Entities_Ledger_Insurance_ClaimBasic, API_V20240412_Entities_Ledger_Payment reason: Records and reads payments posted to patient ledger charges and insurance claims — cash application against customer (patient) invoices, which is accounts receivable management. Not subscription billing, since charges originate from clinical procedures. recovered_from: sweep-20260829T005356Z-edges.json - tag: Webhook Endpoints spec_file: nexhealth-webhook-endpoints-api-openapi.yml capability_id: BC-4270.80 capability_id_l1: BC-4270 capability_name: Webhook & Event Subscription Management confidence: 0.7 evidence: POST /webhook_endpoints Create webhook endpoint; API_V2_Entities_WebhookEndpoint reason: NexHealth is a developer API platform; these operations manage the lifecycle of outbound webhook endpoints that developers register to receive events, which matches Webhook & Event Subscription Management. Confidence moderated because webhook plumbing is generic infrastructure. recovered_from: sweep-20260829T005356Z-edges.json - tag: Webhook Subscriptions spec_file: nexhealth-webhook-subscriptions-api-openapi.yml capability_id: BC-4270.80 capability_id_l1: BC-4270 capability_name: Webhook & Event Subscription Management confidence: 0.7 evidence: POST /webhook_endpoints/{id}/webhook_subscriptions Create webhook subscription; API_V2_Entities_WebhookSubscription reason: Create/edit/delete of event subscriptions attached to webhook endpoints on a developer-facing API platform; matches lifecycle of outbound webhook/event subscriptions. Moderate confidence as this is generic integration plumbing. recovered_from: sweep-20260829T005356Z-edges.json