slug: emis-health
provider: EMIS Health
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: appointments
  spec_file: emis-health-appointments-api-openapi.yml
  capability_id: BC-2800.10
  capability_id_l1: BC-2800
  capability_name: Scheduling & Appointment Management
  confidence: 0.95
  evidence: GET /api/v1/appointments/BookAppointment; CancelAppointment; GetAppointmentSessions; GetSlotsForSession
  reason: Operations book and cancel patient appointments and expose sessions and free slots in a GP clinical
    system — plainly provider-side scheduling and appointment management.
- tag: medicalRecord
  spec_file: emis-health-medicalrecord-api-openapi.yml
  capability_id: BC-2830
  capability_id_l1: BC-2830
  capability_name: Clinical Documentation Management
  confidence: 0.8
  evidence: GET /api/v1/medicalRecord/GetConsultation; GetCodedRecord; POST /api/v1/medicalRecord/FileRecord;
    PATCH UpdateConsultationVisibility
  reason: Read and write access to the active patient record — consultations, coded entries, attachments,
    medication issues — i.e. EHR clinical documentation. Spans several sub-capabilities (note documentation,
    results, record workflow), so mapped at L1 only.
- tag: patient
  spec_file: emis-health-patient-api-openapi.yml
  capability_id: BC-2800.20
  capability_id_l1: BC-2800
  capability_name: Patient Registration Management
  confidence: 0.7
  evidence: GET /api/v1/patient/GetPatientDemographics
  reason: Retrieval of patient demographic and registration data (RegistrationStatusType, RegistrationTypeDead
    schemas) from the GP record — the demographic/identity stewardship of patient registration. Single
    operation, so moderate confidence between registration and MPI.
- tag: patientMatching
  spec_file: emis-health-patientmatching-api-openapi.yml
  capability_id: BC-2900.10
  capability_id_l1: BC-2900
  capability_name: Master Patient Index Management
  confidence: 0.7
  evidence: GET /api/v1/patientMatching/GetMatchedPatients; GetChangedPatients; GetPatientSequence; schema
    PatientMatches37.PatientMatchesPatient
  reason: Operations resolve and synchronise patient identities between a partner system and the EMIS
    record — patient identity matching, the core of master patient index stewardship.