Inside a delivery / Example 01
The record.
And everything behind it.
Follow an observation back to its source. Inspect the schema, review rules and checks that travel with this example release.
Real records are rarely tidy.
This fictional temperature example includes late uploads, gaps and corrections. The structure keeps each distinction visible.
SYN_OBS_0001 / accepted
Baseline
A source-linked observation with both clocks preserved.
Temperature: 36.7 Cel.
- Value
- 36.7 °C
- Event time
- 2020-01-01T07:00:00Z
- Available from
- 2020-01-01T09:00:00Z
- Evidence
- device report
- Source
- SYN_ASSET_0001
- Supersedes
- None
- Clinical review
- Not performed
Eight hand-authored entries, one fictional participant. This demonstrates a delivery format, not clinical results or collected inventory.
Open the package.
Inspect the files here or download the complete release, including the original source text and validation scripts.
README.md
# LifeFrom example delivery v1 All data is fictional. This package demonstrates structure and engineering checks, not clinical evidence, available inventory or model performance. Start with dataset-card.md, then observations.jsonl and source-manifest.json. The eight rows include one intentionally invalid rejected observation. Non-accepted rows are retained to demonstrate audit history and review states. ## Verify Use Python 3.10+ in an isolated environment. Install `jsonschema[format]==4.26.0`, then run `python validate_delivery.py`. Run `python validate_example.py` for the original fixture's negative tests. Validation checks Draft 2020-12 structure, source identity, declared participant membership, source integrity, fixture timestamp evidence, missingness, release rights, demo splits and correction graph integrity. Broad numeric sanity bounds are not clinical validation. Source timestamps are fictional assertions, not authenticated receipt times. Historical selection returns record IDs; do not feed release audit metadata directly into model inputs. The unsupported rejected record must fail the evidence check. The process writes qa-report.json from the observed results. Files also include a data dictionary, annotation guide, split specification, rights summary, checksums and changelog. checksums.json covers payload files except itself. Re-running validation should preserve the report contents. Nothing in this package authorizes training on real patient data or medical decision-making.
Executed checks / This specimen only
Every decision stays traceable.
The package passes its engineering checks, including the expected rejection of the unsupported reading. These checks do not establish clinical validity or model performance.
- Schema and date-time formatsPASS
- Unique record and source IDsPASS
- Manifest identity and cohort membershipPASS
- Source file and evidence integrityPASS
- Fixture source timestamp consistencyPASS
- Explicit missingness and release statesPASS
- Correction graph integrityPASS
- Demo split and release rightsPASS
- Broad numeric sanity bounds, not clinical validityPASS
- Rejection of unsupported valuesPASS
Run the same checks locally with the included instructions. The demonstration has no real consent records, clinical labels or production training licence.