Particle Health and C-CDA Document Exchange

What the source record establishes

Particle Health provides API-based access to clinical records through connected health-information networks, with retrieval, patient matching, normalization, and data products for healthcare organizations.

The maintained taxonomy connects that documented market position to C-CDA Document Exchange. This page keeps the claim at the level supported by the source: Particle Health presents an offering relevant to this work. It does not silently convert a product description into an observed result, a conformity finding, or a universal recommendation.

Current fit signal: Digital-health, provider, and data organizations seeking API-mediated clinical record retrieval should evaluate Particle's allowed purposes, source reach, and data-processing model.

What C-CDA document exchange means in this market

C-CDA Document Exchange should be evaluated as an operating chain rather than a feature label. The chain begins with a named business condition and governed input, passes through configured logic and accountable review, produces an output or action, handles exceptions, and preserves enough evidence for another person to reconstruct the decision later.

Activities that may sit inside the review

• source attribution
• timestamps and status
• data completeness
• transformation lineage
• duplicate and conflict handling
• error correction

Who owns the decision

A capability can be technically available while operating ownership remains fragmented. The evaluation should name the person accountable for policy or business interpretation, the person responsible for configuration and data, the reviewer with authority to resolve exceptions, the approver of release or action, and the owner of monitoring and retirement.

Related domain records commonly place responsibility with clinical informatics, data governance, health information management, integration operations, quality and safety. The local operating model may assign those roles differently, but it should not leave them implicit.

Particle Health should be asked to distinguish what the product decides, what it recommends, what it merely displays, and what remains an organizational judgment. A generic “human in the loop” statement is inadequate unless the human has time, context, evidence, and authority.

Evidence package to request from Particle Health

• The exact product and package proposed, with a dated list of native, integrated, partner, service, and customer-owned components.
• A representative input set, its authoritative source, permitted use, quality checks, and version history.
• The configured workflow from intake through review, exception, approval, action, retention, and export.
• A normal result and at least two difficult exceptions, including one caused by missing or contradictory evidence.
• Role and access definitions for configuration, review, approval, override, monitoring, and administration.
• An implementation map naming integrations, migrations, customer work, provider work, services, test environments, and release gates.
• A retained decision record showing source, logic or model version, user action, timestamps, disposition, and downstream effect.
• A measurement plan with baseline, observation period, population, error threshold, exclusions, and stop condition.

Demonstration script

1. Which exact Particle Health product, edition, module, service, and geography support C-CDA document exchange?
2. What source data, content, rules, and integrations does Particle Health require before the workflow can begin?
3. Where does human judgment enter, and which person can approve, reject, override, or stop the C-CDA document exchange workflow?
4. How does the proposed configuration handle missing data, conflicting evidence, changed rules, and an expired or revoked approval?
5. What record preserves inputs, transformations, user actions, exceptions, outputs, timestamps, and downstream consequences?
6. Which parts are native, partner-delivered, service-delivered, or left to the customer?
7. What can be exported at implementation, audit, renewal, migration, and exit?
8. Which observation would falsify the current fit hypothesis for Particle Health?
9. Can every element be traced to source, time, status, and transformation?
10. How are missing, duplicate, stale, and conflicting values represented?
11. Which data are never requested, not returned, filtered, or unsupported?
12. How do corrections propagate to downstream consumers?

Use the same scenario with every finalist. Let the provider explain differences in architecture, but keep the business condition, required evidence, exception, and expected decision record constant. That makes the evaluation comparable without pretending that unlike products should receive one synthetic score.

Failure modes and boundary conditions

• complete record claims without a defined universe
• transport receipt treated as clinical reconciliation
• silent source overwrite
• one uptime number without service boundary
• successful test treated as durable production operation
• silent error suppression

Record availability depends on permitted purpose, query inputs, source participation, patient matching, network rules, and source-system data. Published coverage does not guarantee a complete longitudinal record.

A buyer should also distinguish absence of public evidence from evidence of absence. If Particle Health has not publicly documented a required detail, the correct status is “not established in this review” until a current, attributable source or direct observation resolves it.

Authority and standards context

Comparable records to inspect

The following organizations also have current official positioning mapped to C-CDA document exchange. Inclusion is a research pathway, not a shortlist or claim of equivalence.

• b.well Connected Health — Clinical Data Network And Record-Retrieval Platform with documented positioning relevant to C-CDA Document Exchange
• Moxe — Clinical Data Network And Record-Retrieval Platform with documented positioning relevant to C-CDA Document Exchange
• Zus Health — Clinical Data Network And Record-Retrieval Platform with documented positioning relevant to C-CDA Document Exchange
• Carequality — Health Information Network And Exchange Framework with documented positioning relevant to C-CDA Document Exchange
• CommonWell Health Alliance — Qualified Health Information Network with documented positioning relevant to C-CDA Document Exchange
• CRISP Shared Services — Community And Public-Health Exchange Infrastructure with documented positioning relevant to C-CDA Document Exchange

Official authority sources

The following primary authority pages support the standards context used in this record. They define an evaluation boundary; they do not endorse Particle Health or establish product conformity.

Conditional conclusion

Particle Health belongs in deeper evaluation for C-CDA document exchange when its documented clinical data network and record-retrieval platform operating model matches the buyer's real workflow, the proposed package contains the required components, and a representative test produces reviewable evidence through normal and exception paths. The conclusion should be reversed or narrowed when the product boundary, source data, authority mapping, integration burden, human decision rights, exportability, or measured result does not meet the stated approval conditions.