slug: canvas-medical provider: Canvas Medical 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: 12 edges: - tag: Appointment spec_file: canvas-medical-appointment-api-openapi.yml capability_id: BC-2800.10 capability_id_l1: BC-2800 capability_name: Scheduling & Appointment Management confidence: 0.9 evidence: POST /Appointment createAppointment Create Appointment; GET /Appointment searchAppointment Search Appointments reason: Operations create, read, update and search patient appointments — plainly appointment booking/scheduling within patient access. - tag: Claim spec_file: canvas-medical-claim-api-openapi.yml capability_id: BC-2870.30 capability_id_l1: BC-2870 capability_name: Claim Production & Submission confidence: 0.78 evidence: POST /Claim createClaim "Create Claim"; GET /Claim searchClaim "Search Claims" reason: FHIR Claim resource creation and search on a provider EHR covering the "financial" domain — production of claims for payer submission within provider revenue cycle. recovered_from: healthcare-vertical-edges.json - tag: Schedule spec_file: canvas-medical-schedule-api-openapi.yml capability_id: BC-2800.10 capability_id_l1: BC-2800 capability_name: Scheduling & Appointment Management confidence: 0.78 evidence: GET /Schedule searchSchedule Search Schedules — FHIR R4 resource in an EHR "supporting scheduling, charting, billing" reason: FHIR Schedule represents provider/resource availability calendars used for appointment booking, which is patient access scheduling. Read-only surface adds slight uncertainty but the meaning is unambiguous in FHIR. - tag: DiagnosticReport spec_file: canvas-medical-diagnosticreport-api-openapi.yml capability_id: BC-2860.60 capability_id_l1: BC-2860 capability_name: Diagnostic Results Management confidence: 0.75 evidence: GET /DiagnosticReport searchDiagnosticReport Search DiagnosticReports reason: DiagnosticReport exposes finalised lab/imaging results for distribution and review, matching diagnostic results management; read-only so modality-specific L2s do not apply. - tag: MedicationRequest spec_file: canvas-medical-medication-request-api-openapi.yml reanchored_from: canvas-medical-medicationrequest-api-openapi.yml capability_id: BC-2830.20 capability_id_l1: BC-2830 capability_name: Computerised Provider Order Entry confidence: 0.75 evidence: POST /MedicationRequest createMedicationRequest Create MedicationRequest; GET /MedicationRequest searchMedicationRequest reason: FHIR MedicationRequest is the prescription/medication order artefact; creating and updating it is computerised provider order entry for medications. Some ambiguity remains as prescriptions also touch pharmacy operations, hence 0.75. - tag: Consent spec_file: canvas-medical-consent-api-openapi.yml capability_id: BC-2910.50 capability_id_l1: BC-2910 capability_name: Patient Rights & Ethics confidence: 0.72 evidence: 'POST /Consent createConsent — Create Consent; schemas: Consent' reason: FHIR Consent captures patient consent/privacy directives and authorisations, which aligns with oversight of patient rights, informed consent processes and advance directives. recovered_from: healthcare-vertical-edges.json - tag: CarePlan spec_file: canvas-medical-care-plan-api-openapi.yml capability_id: BC-2820 capability_id_l1: BC-2820 capability_name: Care Coordination Management confidence: 0.7 evidence: GET /CarePlan searchCarePlan "Search CarePlans"; schemas CarePlan, Period reason: Read-only access to patient care plans in an EHR built for value-based care — care planning is care coordination. L2 withheld since the resource could serve case management or transitions equally. recovered_from: healthcare-vertical-edges.json reanchored_from: canvas-medical-careplan-api-openapi.yml - tag: CareTeam spec_file: canvas-medical-careteam-api-openapi.yml capability_id: BC-2820 capability_id_l1: BC-2820 capability_name: Care Coordination Management confidence: 0.7 evidence: 'GET /CareTeam searchCareTeam Search CareTeams — vendor: "care team coordination"' reason: Care team membership is the coordination-of-care construct across providers; vendor description explicitly cites care team coordination. No single L2 fits cleanly. - tag: Condition spec_file: canvas-medical-condition-api-openapi.yml capability_id: BC-2830 capability_id_l1: BC-2830 capability_name: Clinical Documentation Management confidence: 0.7 evidence: GET /Condition searchCondition — Search Conditions; POST /Condition createCondition reason: FHIR Condition is the problem-list/diagnosis element of the active clinical record, maintained via EHR documentation workflows. Mapped to Clinical Documentation Management at L1 only since no specific sub-capability (note authoring vs. order entry) is named. recovered_from: healthcare-vertical-edges.json - tag: Coverage spec_file: canvas-medical-coverage-api-openapi.yml capability_id: BC-2800.30 capability_id_l1: BC-2800 capability_name: Eligibility & Benefits Verification confidence: 0.7 evidence: 'POST /Coverage createCoverage Create Coverage; schemas: Coverage, Period' reason: FHIR Coverage holds the patient's insurance plan and payer coverage details used to verify benefits before service; sits in eligibility & benefits verification, though it is data storage rather than the verification transaction itself. - tag: Immunization spec_file: canvas-medical-immunization-api-openapi.yml capability_id: BC-2880.20 capability_id_l1: BC-2880 capability_name: Preventive Care & Wellness confidence: 0.7 evidence: 'POST /Immunization createImmunization — Create Immunization; schemas: Immunization' reason: Immunization records document vaccine administration, which sits in preventive care and immunisation management; some overlap with medication administration but immunisation is explicitly named in the preventive care sub-capability. recovered_from: healthcare-vertical-edges.json - tag: Patient spec_file: canvas-medical-patient-api-openapi.yml capability_id: BC-2800.20 capability_id_l1: BC-2800 capability_name: Patient Registration Management confidence: 0.7 evidence: POST /Patient createPatient Create Patient; PUT /Patient/{id} updatePatient; schemas Patient, HumanName, Address, Identifier reason: Creating and maintaining patient demographic and identity records is patient registration/demographic stewardship. Competing reading is master patient index management (BC-2900.10), which keeps confidence at 0.7.