slug: particle-health
provider: Particle 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: 9
edges:
- tag: FHIR
  spec_file: particle-health-fhir-api-openapi.yml
  capability_id: BC-2900.60
  capability_id_l1: BC-2900
  capability_name: Healthcare Interoperability Operations
  confidence: 0.9
  evidence: '"Get Patient $everything", "Create FHIR Patient Query"; "Clinical data is returned in FHIR
    R4 Bundles" — aggregating records from Carequality, CommonWell, eHealth Exchange'
  reason: Operations are FHIR R4 endpoints for retrieving patient clinical records via health information
    exchange networks — squarely Healthcare Interoperability Operations (FHIR endpoints, HIE connections).
- tag: Queries
  spec_file: particle-health-queries-api-openapi.yml
  capability_id: BC-2900.60
  capability_id_l1: BC-2900
  capability_name: Healthcare Interoperability Operations
  confidence: 0.85
  evidence: '"Create Query", "Get Query Status"; description: "asynchronous query orchestration" against
    HIEs and QHIN partners'
  reason: Orchestration of record-retrieval queries to health information exchanges is the core of Healthcare
    Interoperability Operations.
- tag: HL7v2
  spec_file: particle-health-hl7v2-api-openapi.yml
  capability_id: BC-2900.60
  capability_id_l1: BC-2900
  capability_name: Healthcare Interoperability Operations
  confidence: 0.82
  evidence: '"Get HL7v2 Message", "Get HL7v2 Messages by Patient"'
  reason: HL7v2 message retrieval for a patient is health information exchange / interoperability messaging
    operations.
- tag: CCDA
  spec_file: particle-health-ccda-api-openapi.yml
  capability_id: BC-2900.60
  capability_id_l1: BC-2900
  capability_name: Healthcare Interoperability Operations
  confidence: 0.8
  evidence: GET /api/v2/patients/{particle_patient_id}/ccda  getCcdaFiles  Get CCDA Files
  reason: Retrieval of C-CDA clinical documents aggregated from nationwide health information exchanges
    (Carequality, CommonWell, eHealth Exchange), which is exactly the operation of HIE connections and
    interoperable record exchange under Healthcare Interoperability Operations.
- tag: Deltas
  spec_file: particle-health-deltas-api-openapi.yml
  capability_id: BC-2900.60
  capability_id_l1: BC-2900
  capability_name: Healthcare Interoperability Operations
  confidence: 0.8
  evidence: GET /deltas/r4/Patient/{particle_patient_id}/$everything  collectDeltasFhirEverything  Collect
    Deltas FHIR Datasets
  reason: Submits queries to health information exchanges and returns incremental FHIR R4 resources and
    flat datasets — operation of FHIR endpoints and HIE data exchange, i.e. Healthcare Interoperability
    Operations rather than clinical care or coding.
- tag: Flat
  spec_file: particle-health-flat-api-openapi.yml
  capability_id: BC-2900.60
  capability_id_l1: BC-2900
  capability_name: Healthcare Interoperability Operations
  confidence: 0.8
  evidence: '"Submit Flat Patient", "Collect Flat Datasets"; "Clinical data is returned in ... Flat datasets,
    or Deltas (incremental changes)"'
  reason: Alternative representation for retrieving aggregated patient clinical records from HIE networks
    — health information exchange operations.
- tag: NetworkParticipants
  spec_file: particle-health-networkparticipants-api-openapi.yml
  capability_id: BC-2900.60
  capability_id_l1: BC-2900
  capability_name: Healthcare Interoperability Operations
  confidence: 0.72
  evidence: '"Search Network Participants", "Search Network Participants by State"; description: "network
    participant directory search"'
  reason: Directory of participating organisations in the nationwide exchange networks — part of operating
    health information exchange connections.
- tag: Documents
  spec_file: particle-health-documents-api-openapi.yml
  capability_id: BC-2900
  capability_id_l1: BC-2900
  capability_name: Health Information Management
  confidence: 0.7
  evidence: POST /api/v1/documents  submitDocument; GET /api/v1/documents/patient/{id}  getPatientDocuments
  reason: Submission, retrieval and deletion of patient clinical documents within an interoperability
    platform — clearly health information management, but the surface is thin as to whether this is exchange
    operations (BC-2900.60) or record lifecycle (BC-2900.40), so only the L1 is asserted.
- tag: Patients
  spec_file: particle-health-patients-api-openapi.yml
  capability_id: BC-2900
  capability_id_l1: BC-2900
  capability_name: Health Information Management
  confidence: 0.7
  evidence: POST /api/v2/patients  submitPatient; POST /api/v2/patients/search  searchPatient — 'The API
    surfaces patient registration'
  reason: Patient demographic submission and matching used to identify a patient across exchange networks
    sits in health information management; unclear whether this is best read as MPI stewardship or interoperability
    operations, so only the L1 is asserted.
  recovered_from: healthcare-vertical-edges.json