Built to be checked
What DermLiving is for, where it stops, and how its knowledge and your data are handled.
Intended use
DermLiving is reference knowledge for software developers, and it never makes the clinical call.
Built for
- Clinical reference copilots
- Documentation and coding
- Medical education
- Research discovery
Not for
- Diagnosis
- Malignancy scoring
- Treatment selection or dosing
- Autonomous triage
DermLiving is not a medical device. Clinical decisions stay with qualified professionals.
Where it abstains
Out-of-scope questions get a machine-readable reason instead of a guess, so your product can respond well.
Every abstention returns status abstained, its reason, a null answer and no citations.
| Reason | Fires when | Response contains |
|---|---|---|
clinical_decision | A clinical decision is asked for | A note on clinical scope |
insufficient_evidence | No passage supports an answer | The version it searched |
patient_data | Input holds patient identifiers | A note that nothing was stored |
{ "question": "Which treatment should this patient start?" }
1{
2 "data": {
3 "status": "abstained",
4 "reason": "clinical_decision",
5 "answer": null,
6 "message": "Treatment and diagnosis are clinical decisions. DermLiving returns reference knowledge only.",
7 "citations": []
8 },
9 "meta": {
10 "request_id": "req_gl4xweaG8F",
11 "knowledge_version": "kv_2026_10_01"
12 }
13}
Provenance you can check
Every passage carries its source, version, locator, checksum and license, so any citation can be traced.
In adolescents and adults, atopic dermatitis most often involves flexural skin, including the antecubital and popliteal fossae, as well as the neck, face and hands.
- source
- The publisher record
- src_sbx_ad_overview
- version
- The exact source release
- sv_2026_09_14
- locator
- Section and paragraph
- Distribution, para 2
- checksum
- SHA-256 of the passage text
- sha256:b2bb063ee133
- license
- The rights record behind it
- lic_sbx_synthetic
Before and after indexing
- Rights checked firstNo source is indexed before its license clears.
- Immutable versionsA published knowledge version never changes.
- Pin any versionPinned requests return the same sources.
- Revocation propagatesRevoked sources leave every active index.
Each source's rights are licensed one by one, and a source is used only as far as its license reaches. The API returns the same five fields on every source.
- store
- embed
- display_snippets
- display_full_text
- train
Release gates
A knowledge version ships only when it clears every gate below. These are thresholds it must meet, not reported results.
| Gate | Measures | Threshold |
|---|---|---|
| Citation validity | Every citation resolves to a real passage | ≥ 99% |
| Claim grounding | Claims supported by their cited passage | ≥ 95% |
| Curated recall | Relevant passages found in the top 10 | ≥ 95% |
| Correct abstention | Out-of-scope questions abstain | ≥ 95% |
| Cross-tenant exposure | Adversarial suite, every release | 0 |
| Unauthorized tool runs | Adversarial suite, every release | 0 |
Designed controls
The controls the platform is built around, from how keys are stored to how builds are signed.
- Scoped API keysHashed at rest, least-privilege and rotatable.
- Tenant isolationEnforced in the database and the application.
- EncryptionIn transit and at rest, with managed secrets.
- No PHI in telemetryLogs and traces carry no patient data.
- Tool authorizationPer-tool scopes, approval for consequential actions.
- Audit trailsRequests, tool calls and approvals are recorded.
- Supply chainDependency scanning, an SBOM and signed builds.
The sandbox accepts no patient data. A production workflow that handles PHI starts only after a signed agreement and a security and clinical review.
Common questions
What clinical leads, security reviewers and buyers ask first.
Is DermLiving a diagnosis API?
No. It returns reference knowledge: structured conditions, terminology maps, cited evidence and grounded answers. It never diagnoses, scores malignancy, selects or doses treatment, or triages. Questions that ask for those return an abstention with reason clinical_decision.
Does the sandbox contain real patient data?
No. The sandbox serves synthetic records only, published as DermLiving Sandbox Reference, and it accepts no patient data. Input that appears to hold patient identifiers returns an abstention with reason patient_data.
Can I use it for medical decisions?
No. DermLiving informs the software people use, and clinical decisions stay with qualified professionals. Every answer carries its citations so a reader can check the source behind each claim.
Where does the knowledge come from?
From rights-cleared sources. Each source is tracked with its license, version and checksum, and it passes a rights check before it is indexed. Every passage the API returns names its source, version, locator, checksum and license.
What happens when evidence is missing?
The API abstains with reason insufficient_evidence and returns no answer and no citations. It does not fill the gap with an unsupported claim.
Which terminologies are supported?
ICD-10-CM and ICD-11. Lay terms, abbreviations and codes resolve to one concept, and ambiguous input is flagged instead of guessed.
Do you train models on my queries?
No. Your queries and the responses to them are not used to train models.
Start in the sandbox.
The whole API on synthetic data. No key, no card, no patient data.