How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Sectra website screenshot

Sectra

Sectra is a Swedish medical technology company providing an enterprise imaging platform (PACS/VNA) for radiology, pathology, cardiology, orthopaedics, and other -ologies. Integration is delivered through established healthcare interoperability standards rather than a single open developer API - DICOM and DICOMweb for imaging, HL7 for orders/results messaging, IHE XDS for cross-enterprise document sharing, FHIR/FHIRcast for clinical context synchronization, and a Web Content API for embedding third-party content and applications into the diagnostic viewer. AI and third-party applications integrate through the Sectra Amplifier Marketplace / Amplifier Services ecosystem. Sectra's API and integration surface is partner- and customer-gated (deployed per-site, no public self-service developer portal); the API entries below are honestly modeled from Sectra's documented standards and interfaces, not scraped from an open OpenAPI catalog. Sectra also authored the first open-source FHIRcast sandbox and reference implementation.

human only

Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.

Kin Score

API Evangelist profiles Sectra the way a machine reads it — 7 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Sectra scores 8.5/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance. Every facet and dimension name is a link: it opens that measurement's page on APIs.io, where the rating runs across the whole catalog — the exact checks that feed it, how every profiled provider distributes on it, and who is at the top of it.

Kin Score Kin Score How this is scored →
scored 2026-09-08 · rubric v0.20.0
Sectra Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from Sectra's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.

<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/sectra-imaging/"
   title="Sectra on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/sectra-imaging.svg"
       alt="Sectra Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile Sectra

Each block below is one kind of artifact we hold for Sectra. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

APIs 5

Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.

Individual APIs this provider publishes, each with its own machine-readable definition.

Sectra DICOMweb API

Web-based access to imaging studies, series, and instances using the DICOM standard's RESTful services - QIDO-RS (query), WADO-RS (retrieve), and STOW-RS (store). Sectra's enter...

Sectra HL7 Integration Interface

HL7 v2 messaging interface for exchanging orders, scheduling, worklist, and results/reports between Sectra PACS/RIS and surrounding EMR/RIS systems. This is a message-based (typ...

Sectra FHIRcast Interface

Clinical context synchronization using the FHIRcast standard, which Sectra helped originate (with Epic) and for which Sectra published the first open-source sandbox and referenc...

Sectra Web Content API

Web Content API for embedding third-party web content, results, and applications into the Sectra diagnostic viewer in patient/study context, and for launching Sectra in context ...

Sectra IHE XDS Interface

IHE Cross-Enterprise Document Sharing (XDS/XDS-I) interface for registering, querying, and retrieving imaging documents and manifests across enterprise boundaries. A profile-bas...

Security Posture 2

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Sectra Imaging Domain Security

TLSv1.3 · HSTS · DNSSEC · DMARC

SECURITY

Sectra Imaging Vulnerability Disclosure

security.txt · contact published

SECURITY

Resources

Every other property we hold for Sectra — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Documentation 2

Reference material describing how the API behaves

Build 1

SDKs, sample code, and the tooling you integrate with

Access & Security 2

Authentication, authorization, and security posture

Company 3

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/sectra-imaging · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of Sectra, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.