fulcra-lab-results

Parse lab-report PDFs into validated per-marker Fulcra data tracks.

10|1|Updated May 21, 2026
One-click install
npx skills add https://github.com/ashfulcra/fulcra-tools --skill fulcra-lab-results-ashfulcra
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fulcra-lab-results
Source: https://github.com/ashfulcra/fulcra-tools/tree/main/skills/fulcra-lab-results
Command: npx skills add https://github.com/ashfulcra/fulcra-tools --skill fulcra-lab-results-ashfulcra

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Lab results arrive as PDFs from different providers (LabCorp, Quest, hospital labs) with inconsistent marker names and units, making it impossible to build a single longitudinal history per biomarker without manual transcription and unit conversion. ## Core Features & Use Cases - Dual-pass PDF extraction: Transcribe each lab report twice independently, then cross-check the passes with the fulcra-labs engine to catch transcription errors before anything is written. - Deterministic normalization: The engine resolves marker aliases, converts units to canonical forms, sanity-checks values against physiologic bounds, and computes idempotent source ids so re-runs are safe no-ops. - Verify-before-ingest workflow: Every row gets an ok/review/reject verdict in a dry run; nothing reaches Fulcra without passing validation or explicit operator confirmation. - Use Case: Hand the agent a LabCorp PDF and say "parse my labs" — LDL-C, HbA1c, and TSH results land on the same canonical tracks as previous Quest results, forming one queryable time series per marker. ## Quick Start Save your lab-report PDF locally and ask the agent to parse it into Fulcra tracks, then review the validation verdicts and confirm before ingestion.

Frequently Asked Questions about fulcra-lab-results

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I import LabCorp or Quest results into Fulcra?

Save the lab-report PDF locally and hand its path to the agent. The agent transcribes it twice, cross-checks the passes with fulcra-labs check, dry-runs validation, and ingests only after you confirm the verdict table.

How does lab PDF parsing handle different units like mmol/L versus mg/dL?

The fulcra-labs engine converts each value to the marker's canonical unit, such as glucose 5.5 mmol/L to 99.1 mg/dL. The agent never converts or rounds during transcription; unrecognized units are held for review.

Can I fetch lab PDFs directly from the LabCorp or Quest patient portal?

No. Portal fetch is a planned future feature and is not currently supported. You must download the PDF from the portal yourself and provide the local file path to the agent.

What happens if a lab value fails validation during ingest?

Rows receive ok, review, or reject verdicts. Review rows (ambiguous markers, missing units, implausible values) require explicit operator confirmation via --yes-reviewed; reject rows such as non-numeric values are never ingested.

Is my medical data uploaded when parsing lab reports?

Only the numeric values you explicitly confirm are written to your Fulcra account. Source PDFs are archived locally in ~/.config/fulcra-labs/documents/ on your machine and are never uploaded.

What happens if I re-run ingestion on the same lab report?

Re-running is safe. The engine computes a deterministic source id from marker, collection time, and canonical value, so re-ingesting the same report is a server-side no-op with no duplicate records.