slug: ritten
provider: Ritten
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: 4
edges:
- tag: calendar
  spec_file: ritten-calendar-api-openapi.yml
  capability_id: BC-2800.10
  capability_id_l1: BC-2800
  capability_name: Scheduling & Appointment Management
  confidence: 0.75
  evidence: POST /calendar/events/list  Query calendar events; POST /calendar/events  Create a new calendar
    event
  reason: Ritten is a behavioral-health EMR whose product covers scheduling; the tag exposes creation
    and querying of calendar events, i.e. appointment/resource scheduling. Slight ambiguity as the events
    are generic calendar objects, hence 0.75.
  recovered_from: healthcare-vertical-edges.json
- tag: forms
  spec_file: ritten-forms-api-openapi.yml
  capability_id: BC-2830
  capability_id_l1: BC-2830
  capability_name: Clinical Documentation Management
  confidence: 0.72
  evidence: POST /patients/{id}/forms  postPatientForm  Create a form on a patient chart and submit field
    values; GET /forms/definitions (schemas FormDefinitionSignatureRequirement, PatientFormSection)
  reason: Structured form instances written onto the patient chart with signature requirements are clinician
    documentation in the health record. L1 only as forms span notes/assessments rather than one named
    sub-capability.
- tag: patients
  spec_file: ritten-patients-api-openapi.yml
  capability_id: BC-2800.20
  capability_id_l1: BC-2800
  capability_name: Patient Registration Management
  confidence: 0.7
  evidence: POST /patients  createPatient  Create a new patient; schemas PatientDemographics, PatientName,
    Insurance, Address; GET /patients/external/{externalId}
  reason: Creation and stewardship of patient demographic, identity, insurance and relationship data is
    patient registration/record establishment. Some operations (vitals, chart attachments) spill into
    clinical documentation, so confidence is moderate.
- tag: users
  spec_file: ritten-users-api-openapi.yml
  capability_id: BC-620.20
  capability_id_l1: BC-620
  capability_name: Identity & Access Management
  confidence: 0.7
  evidence: POST /users/{id}/roles Assign a role to a user; DELETE /users/{id}/roles/{roleID} Remove a
    role from a user; GET /staff List all clinic staff users
  reason: User account lifecycle and role assignment for clinic staff and teams — identity and access
    administration, not medical staff credentialing (no privileging, verification, or peer-review operations
    appear).
  recovered_from: healthcare-vertical-edges.json