Primary sources first
Vendor documentation, official developer portals, certification records, and published endpoint directories anchor each record.
Research standard
Evidence before verdict.
The unit of analysis is not “Does this EHR have an API?” It is the product, operation, integration path, access requirement, execution surface, verifier, and source.
No negative inference
If a write operation is absent from reviewed public docs, we say exactly that. We do not convert absence into unsupported.
Operation-specific
A platform may expose one write and gate another. Product-wide yes/no labels are avoided when the evidence is narrower.
Status vocabulary
Documented
An official public source describes the relevant path. Exact operation and deployment still require validation.
Partner-gated
The route exists through a developer, marketplace, licensing, or authorized-vendor program.
Site-specific
Capability or access materially depends on product edition, customer approval, tenant configuration, or operation.
Not found publicly
The reviewed public sources did not establish the claimed path. This is not proof that it is unsupported.
Unknown
The public evidence is insufficient to make a narrower claim.
Coverage and corrections
The launch dataset favors vendors with useful public evidence. It is not a market-share ranking or a complete catalog. Each record carries a review date. To challenge a record, send an official source URL, the product and version, the exact operation, and the access context.
Submit a correction