...  we have not stopped looking

Physician
Portal

Secure access to the Medical Research Solitaire Engine — clinical decision support built on cross-domain drug hypothesis intelligence.

🔒 HIPAA Compliant ⚕️ Licensed Physicians Only 🧬 MRS Engine v2.0
Foundry One Sciences LLC  ·  Delaware  ·  SDVOSB  ·  Micro Entity
...  we have not stopped looking
Business Associate Agreement
Required before accessing the Physician Portal · Please read carefully and scroll to bottom
↓ Scroll to read the full agreement before signing

BUSINESS ASSOCIATE AGREEMENT

This Business Associate Agreement ("BAA") is entered into between Foundry One Sciences LLC, a Delaware Limited Liability Company ("Business Associate"), and the undersigned licensed healthcare provider ("Covered Entity / Physician").

1. Definitions

Protected Health Information (PHI) means any individually identifiable health information as defined under 45 C.F.R. § 160.103. De-identified Information means health information processed to remove all 18 HIPAA Safe Harbor identifiers per 45 C.F.R. § 164.514(b).

2. Obligations of Business Associate

Foundry One Sciences LLC agrees to: (a) not use or disclose PHI other than as permitted; (b) use appropriate safeguards; (c) report any breach within 72 hours; (d) ensure subcontractors agree to equivalent restrictions; (e) make records available to HHS; (f) return or destroy PHI upon termination.

3. Permitted Uses and Disclosures

Business Associate may use PHI solely to perform research intelligence services. PHI will be de-identified prior to MRS Engine processing. No PHI will be used for unrelated purposes.

4. Security Obligations

AES-256 encryption at rest, TLS 1.3 in transit, MFA-enforced portal access, immutable audit logging, and automatic session timeout after 15 minutes.

5. Term and Termination

Effective upon electronic acceptance. Either party may terminate upon 30 days notice. PHI destroyed within 30 days of termination with written certification.

6. Governing Law

Governed by HIPAA/HITECH and the laws of the State of Delaware.

Access Not Granted

You must accept the Business Associate Agreement to access the portal.

Questions? Contact: fredcover@foundryonesciences.org

...  we have not stopped looking
Logged in as Dr. Smith
Overview
Welcome back, Dr. Smith — your practice dashboard
Total Queries
14
Since enrollment
Briefs Delivered
12
To physician email
In Progress
2
Awaiting MRS output
JELLO Depth Avg
Blue
Cross-domain level
Recent Activity
Brief delivered — Token MRS-0019 · Metabolic / Insulin Resistance
2h ago
Query submitted — Token MRS-0020 · Cardiovascular comorbidity w/ T2DM
4h ago
New case intake — MRS-0021 · Pending de-identification
Today 9:14am
Brief delivered — Token MRS-0018 · Neurological / Cognitive Decline
Yesterday
Practice enrolled — BAA accepted and on file
Mar 10
New Patient Query
MRS Clinical Profile Intake Form v3.0 — Token-Only Protocol
Foundry One Sciences LLC — Medical Research Solitaire Engine

Clinical Profile Intake Form

...  we have not stopped looking
Version 3.0  ·  Initial Patient Consultation  ·  Token-Only Protocol
CRITICAL — TOKEN-ONLY PROTOCOL: Do NOT enter patient name, date of birth, address, phone number, insurance number, or any personal identifier anywhere in this form. Use the physician-assigned Patient Token only. MRS never receives or stores patient identity. The physician maintains the sole link between the token and the patient.
This is a first introduction. Complete every section as you would a comprehensive patient handoff to a new specialist. The MRS Engine has no prior knowledge of this patient — thoroughness directly determines output quality. Follow-up submissions will be significantly shorter.
Section A

For Office Use Only

Completed by staff before handing to physician
Section B

Primary Clinical Presentation

Completed by the physician
Write as you would for a specialist colleague seeing this patient for the first time. Minimum word counts are enforced on narrative fields and shown below each one. The engine reads your clinical language directly — specificity and detail produce better output.
Biomarker / Vital SignValueUnitReference RangeDateFlagDelete
Condition / DiagnosisICD-10Duration (months)DomainStatusDel
Treatment / InterventionDuration (mo)OutcomeWhy DiscontinuedSpecialtyDel
ConditionFatherMotherSibling(s)Grandparent(s)Age of OnsetUnknown / N/A
Cancer — specify type
Cardiovascular disease
Neurological disorder
Metabolic / Diabetes
Autoimmune condition
Mental health condition
Rare / genetic disorder
Other — specify
B.10 — Clinical Anomaly

The One Finding That Does Not Fit

Minimum 50 words — primary trigger for caution signal
Highest-value field on this form — minimum 50 words required Describe the single clinical finding, symptom, lab value, response pattern, or behavioral anomaly that does not fit the standard presentation of the primary diagnosis. The thing that keeps you up at night. The result you circled on the lab report. The symptom that doesn't fit any of the boxes. This is the primary trigger for the PROCEED WITH CAUTION signal. Write None clearly if nothing is anomalous — do not leave this field blank.
Section C

Current Medications

All prescriptions, OTC medications, and supplements
Include every medication, supplement, and vitamin — even occasional ones. Drug interaction cross-domain signals frequently emerge from combinations that seem unrelated. Dosage must be numeric.
Medication / Supplement NameDosageUnitFrequencyDuration (mo)Prescribing SpecialtyDelete
Section D

Laboratory Values and Diagnostics

Numeric values only — do not filter for relevance
Enter all available lab values — do not filter for what seems relevant. Cross-domain biomarker signals are often found in results physicians consider unremarkable. Flag: H = High   L = Low   C = Critical   N = Normal
Lab Test / BiomarkerResult (numeric)UnitReference RangeDateFlagDelete
Section E — Gate Field

Physician Mechanistic Hypothesis

75 words minimum — form gates on this field
FORM DOES NOT SUBMIT WITHOUT 75 WORDS MINIMUM IN THIS SECTION Write as a physician thinking out loud to a trusted colleague. What biological mechanism do you believe underlies this patient's presentation? What connections between their conditions, medications, lab anomalies, and clinical history do you suspect? What would you test if you had unlimited diagnostic resources? What published research have you read that feels relevant but you can't quite place? A generic chart summary does not satisfy this requirement. The engine is looking for your clinical intuition — the reasoning that isn't in the chart.
Section F

Physician Attestation and Signature

By submitting, the physician confirms: (1) Clinical data is accurate to the best of their knowledge as of the date submitted; (2) The research output will be reviewed as research intelligence only and does not replace independent clinical judgment; (3) All clinical decisions arising from the output remain the sole responsibility of the reviewing physician; (4) This submission complies with the token-only protocol — no patient personal identifiers are included; (5) The mechanistic hypothesis in Section E reflects independent physician clinical reasoning.
Section E needs 75 words · Attestation not confirmed

Foundry One Sciences LLC  ·  MRS Clinical Profile Intake Form v3.0  ·  Token-Only Protocol  ·  foundryonesciences.com  ·  302-416-1854

Active Cases
All queries submitted by this practice
HIPAA & Compliance
Current security posture and architecture overview
🔐
Encryption
AES-256 at rest · TLS 1.3 in transit. PHI never stored in plaintext. Intake Vault isolated from MRS Engine layer.
📛
Authentication
NPI-based login with MFA enforcement. Session timeout: 15 min. Failed login lockout: 5 attempts.
⚖️
De-identification
Safe Harbor per 45 C.F.R. § 164.514(b). 18 identifiers stripped. Token assigned. PHI never enters MRS Engine.
📋
Audit Logging
Immutable event log. HIPAA retention: 6 years. Breach alert: 72-hour notification policy.
Compliance Status
Business Associate Agreement✓ Accepted & on file
PHI Handling Protocol✓ Active
SaMD Output Framing✓ Enforced on all briefs
Audit Log✓ Running
Breach Response Plan✓ On file — 72h notification