Twinome AIBack to today
Your Passport

Passport connections

Bring in only the context you choose.

Connections add helpful clues to your medication picture. They never get a copy of your Passport.
You choose what to connect Twinome asks before sharing anything Context is not a diagnosis

Choose a path

Add yourself

Synthetic demo record

Your medication notes

Medication, allergy, side-effect, and access notes can complete your medication picture.

Allowed data
Only what you choose to add
Used for
Your medication picture
Current state
Self-reported
What Twinome will not inferTwinome keeps your note distinct from a clinician-confirmed record.

Choose a path

Upload a demo file

Demo file available

23andMe upload

A consumer genotype file can identify medication-relevant gaps worth confirming.

Allowed data
Selected consumer markers
Used for
Confirmation planning
Current state
Incomplete callability
What Twinome will not inferTwinome does not treat a consumer upload as a complete clinical result.
Demo file available

AncestryDNA upload

An archived consumer genotype file can surface a medication question to discuss.

Allowed data
Selected consumer markers
Used for
Confirmation planning
Current state
One-time file import
What Twinome will not inferTwinome never fills in missing genomic information.
Demo report available

Clinical PGx report

A verified pharmacogenomic report can support a clinician conversation when it is relevant.

Allowed data
Reported gene-drug findings
Used for
Medication review
Current state
Sample report only
What Twinome will not inferTwinome does not turn a report into a medication instruction.

Choose a path

Connect with permission

Oura logoConnected in this demo

Oura

Sleep and readiness can add context when you say something feels different.

Allowed data
Sleep timing and readiness trends
Used for
Care conversation
Current state
Limited history
What Twinome will not inferA sleep trend is not proof that a medicine caused it. Oura receives no Passport data.
Flo logoPermission paused

Flo

Optional cycle timing can help you bring useful context into a care conversation.

Allowed data
Nothing while permission is paused
Used for
Not active
Current state
No data is used
What Twinome will not inferTwinome does not infer a diagnosis, pregnancy, or treatment decision from cycle context.
Apple Health logoConnected in this demo

Apple Health

Medication and symptom observations can support your own medication picture.

Allowed data
Only the health data you allow
Used for
Medication picture
Current state
Not every event is shared
What Twinome will not inferA missing Health record is unknown, not proof that something did not happen.
WHOOP logoAvailable as a demo

WHOOP

Recovery and sleep patterns can add context to a conversation you choose to have.

Allowed data
Recovery and sleep summaries
Used for
Care conversation
Current state
Not connected
What Twinome will not inferTwinome does not treat training or recovery data as a clinical finding.
Bevel logoIllustrative connection

Bevel

Wellness trends could be used only as optional context for your own care conversation.

Allowed data
Selected wellness summaries
Used for
Care conversation
Current state
No live connection
What Twinome will not inferTwinome does not diagnose or make treatment decisions from wellness trends.

Choose a path

From care and coverage

Sync delayed

Pharmacy history

A fill pattern can help spot an access barrier before assuming a medicine is not working.

Allowed data
Program-scoped fill events
Used for
Access support
Current state
Latest sync unavailable
What Twinome will not inferA refill gap may reflect cash pay, another pharmacy, or missing data.
Illustrative connection

Community pharmacy

A pharmacy could contribute dispensing context after you approve a focused request.

Allowed data
Dispense and refill status
Used for
Medication review
Current state
No live connection
What Twinome will not inferTwinome does not assume a dispensed medicine was taken.
Program-limited demo

Payer patient access

Member-authorized records can help clarify coverage and access support.

Allowed data
Plan-scoped claims and benefits
Used for
Access support
Current state
Program rules apply
What Twinome will not inferCoverage data is not available for general commercial targeting.
Illustrative connection

Payer / PBM

A program could contribute formulary and coverage context under its contract.

Allowed data
Program-specific benefit context
Used for
Access support
Current state
No live program
What Twinome will not inferTwinome does not reuse payer data outside its permitted purpose.
Mock launch only

Care records

A participating clinic could contribute a focused medication record when you allow it.

Allowed data
Medication, allergy, and relevant observation data
Used for
Medication review
Current state
No live record in this demo
What Twinome will not inferTwinome does not claim an EHR connection until you see and approve it.
Illustrative connection

Epic / Oracle Health

A health-system workflow could open a focused clinical view in patient context.

Allowed data
Scoped clinical snapshot
Used for
Treatment
Current state
No health-system deployment
What Twinome will not inferTwinome does not overwrite a source EHR medication list.
Scan demonstration

Emergency point of care

A scoped Passport scan can surface key medication information in an urgent moment.

Allowed data
Patient-approved emergency snapshot
Used for
Emergency review
Current state
Network required for full view
What Twinome will not inferA QR scan alone is not universal consent or a full offline record.
Illustrative connection

Clinical PGx lab

A clinical laboratory could contribute verified pharmacogenomic findings.

Allowed data
Verified PGx result summary
Used for
Medication review
Current state
No lab connection
What Twinome will not inferTwinome keeps consumer uploads and clinical PGx results separate.
Demo connections, real boundaries

These previews use only synthetic fixture data. In a production product, each connection would use a secure approved sign-in or upload flow. Twinome never asks for a personal API key.

Oura, Flo, WHOOP, Bevel, Epic, and Oracle Health are illustrative integration targets only. No relationship, endorsement, or live connection is implied.