Starling
Starling-branded reports and service experience.
One operating model, configured around each programme
A preventive clinic, general practice group, hospital, and research cohort do not need the same front end or assay. They do benefit from the same traceable backbone.
From request to report
A complete Polygenic Scores as a Service pathway
Every PRS programme follows the same traceable operating model, while data intake, scoring, interpretation, delivery, and integrations remain configurable.
-
01
Request
Clinical, research, portal, or API-led intake.
-
02
Sample
Consent, logistics, activation, and tracking.
-
03
Assay
Fit-for-purpose platform and laboratory route.
-
04
Analysis
Quality control, bioinformatics, and versioned pipelines.
-
05
Interpretation
Evidence and context translated for the intended setting.
-
06
Delivery
Reports, structured data, and system integration.
Security · traceability · version control · quality documentation · evidence management
Under your brand or ours
A delivery model that fits the organisation
The experience can be visibly Starling, co-branded, or embedded behind the customer brand while the scientific and operational foundation remains controlled.
Co-branded
A shared clinical or programme identity.
White-label
Customer-branded portals, reports, and delivery.
Configurable experience
- Brand and domain
- Languages and report layers
- Order and notification flows
- Delivery formats and integrations
Controlled foundation
- Quality control
- Traceability and audit trail
- Evidence and version management
- Security and data governance
Integration layer
Designed to sit between source and destination systems
Orders can originate in portals, clinical systems, laboratory environments, or controlled file flows. Results can return as readable reports, professional appendices, structured data, or partner-specific integrations.
1 · Source systems
Controlled intake of orders, genotype data, and programme context.
- EHR / HIS
- Care platform
- LIMS
- Partner portal
- Research platform
2 · Starling PRS service
Orchestration from PRS request to governed delivery.
- 01Request
- 02Sample
- 03Assay
- 04Analysis
- 05Interpretation
- 06Delivery
3 · Destination systems
Results return in the format and system the organisation needs.
- Clinical report
- Professional QC
- EHR / LIMS
- Data warehouse
- API / structured data
Operational integration layer
Healthcare system integration
Starling's order and reporting environment is designed to connect securely with the systems partners already use, including EHR/EPD environments, primary-care systems, care platforms, laboratory systems, partner portals, and data warehouses. Requests, sample states, status updates, and reports can be exchanged efficiently while authorization, logging, access control, and data protection remain centrally governed.
Plug-and-play
Operational integration model
APIs
Orders, samples, and status flows
Secure routes
Reports, messages, and file exchange
EHR, HIS, care, and partner platforms
Interfaces can be configured around existing clinical, primary-care, laboratory, and partner-platform workflows, so PRS services can be added without replacing core systems.
Orders, samples, and status updates
Secure APIs support order flows, sample activation, processing states, and implementation-specific notifications for partners and laboratories.
Reporting and secure delivery
Reports and results can be delivered through protected download routes, secure messaging, controlled file transfer, or partner-specific reporting paths.
Central authorization and audit trail
Reports and results are not shared directly from storage. Access runs through protected routes with authentication, authorization, logging, audit trails, and data minimization.
- Secure API connections
- Secure report downloads
- Controlled file exchange
- Data warehouse exports
- Portal-facing delivery
Design a PRS workflow around your organisation
Use the contact form and we will send your message to the right part of the team.
Contact