slug: kno2
provider: Kno2
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: Messaging
  spec_file: kno2-messaging-api-openapi.yml
  capability_id: BC-2900.60
  capability_id_l1: BC-2900
  capability_name: Healthcare Interoperability Operations
  confidence: 0.75
  evidence: POST /api/messages/{id}/send  sendMessage  Send a message ... SEND, RECEIVE, and FIND patient
    information - Direct Secure Messaging, clinical document exchange
  reason: Composing and sending clinical documents about a Patient over Direct Secure Messaging / national
    exchange networks realises provider-side healthcare interoperability operations (exchange of protected
    health records between organisations).
- tag: Intake
  spec_file: kno2-intake-api-openapi.yml
  capability_id: BC-2900.60
  capability_id_l1: BC-2900
  capability_name: Healthcare Interoperability Operations
  confidence: 0.72
  evidence: 'GET /api/messages  searchMessages  Search / find messages; schemas: Patient, Attachment,
    Message'
  reason: Inbound retrieval and processing of clinical messages carrying patient documents across Direct/Carequality/TEFCA
    is the operation of health information exchange connections, i.e. healthcare interoperability operations,
    rather than clinical documentation authoring.
- tag: Attachments
  spec_file: kno2-attachments-api-openapi.yml
  capability_id: BC-2900.60
  capability_id_l1: BC-2900
  capability_name: Healthcare Interoperability Operations
  confidence: 0.7
  evidence: Through a single Communication API you SEND, RECEIVE, and FIND patient information - Direct
    Secure Messaging, clinical document exchange, HL7 FHIR ... GET /api/messages/{id}/attachments/{attachmentId}  Retrieve
    an attachment
  reason: Attachments are the clinical documents exchanged over a health information exchange / QHIN network,
    so the surface operates provider-side interoperability. Slight ambiguity as the operations themselves
    are generic message-attachment CRUD.
- tag: Directory
  spec_file: kno2-directory-api-openapi.yml
  capability_id: BC-2900.60
  capability_id_l1: BC-2900
  capability_name: Healthcare Interoperability Operations
  confidence: 0.7
  evidence: GET /api/directory/validate  validateAddresses  Validate Direct addresses; GET /api/documenttypes  listDocumentTypes  List
    document types
  reason: Directory validation of Direct Secure Messaging addresses and supported clinical document types
    is part of operating health information exchange connections for a provider — healthcare interoperability
    operations. It is a supporting lookup surface, hence moderate rather than high confidence.