Source and processing history
Trace clinical records to their sources and review validation decisions, mappings, and subsequent handling.
Home Trust is built.
THE TRUST FRAMEWORK
Trust is built.
Make it visible.
Understand the clinical information you receive: where it came from, which checks it passed, what changed, and what still needs attention. LYNQSYS makes that evidence part of clinical data management.
Explore the frameworkTHE INTERSTELLA TRUST MODEL
QualityUsable data+GovernanceDefensible handling
EvidenceConfidence you
can inspect.
can inspect.
Conformity · Completeness · Consistency
Provenance · Contextual integrity
Trust Model
Trust = quality + data governance
Clinical records arrive from independent systems with different formats, terminology, identifiers, and levels of completeness. LYNQSYS brings them together through its Referential Data Refinery, preserving quality signals and handling history so receiving teams can assess the information for a specific use.
Exception handling
Identify messages that need attention, support stewardship and remediation, and retain visibility through replay.
Quality review
Inspect completeness, consistency, and conformance signals as clinical information is processed.
Governed delivery
Define access, publication, and receiving-system requirements for the clinical information being shared.
DTRF Trust Dimensions
Five dimensions. A clearer picture of trust.
The Data Trust and Refinery Framework (DTRF) organizes quality checks and governance evidence within LYNQSYS across five dimensions. Review each dimension against the requirements of the receiving application and its intended use.
1. Conformity
Evidence that data conforms to expected structure, format, and applicable standards. Conformance checks are applied before data moves downstream.
2. Completeness
Evidence that required data elements are present. Gaps are surfaced and recorded rather than silently passed through.
3. Consistency
Evidence that data is internally consistent across fields, encounters, and related records. Conflicts are identified and handled explicitly.
4. Provenance
Evidence of where data originated and how it moved. Lineage and traceability are maintained so downstream teams can inspect handling history.
5. Contextual Integrity
Evidence that data was interpreted and processed with reference- aware and standards-aware context in mind. Contextual handling improves interpretability beyond syntactic normalization.
Traceability Sample
See the history behind the data.
When a clinical value looks unexpected, trace it to the source and review the checks, mappings, and corrections that produced it. This illustrative laboratory message shows the handling evidence an operations team can review.
ILLUSTRATIVE CLINICAL MESSAGE
Traceability record preview
Published after review
Source
An HL7 laboratory message contains a local test code.
Validation
An unmapped code is identified; the message needs review.
Resolution
The mapping is reviewed and corrected; the message is replayed.
Lineage
Source context, the mapping decision, and replay history are retained.
Publication
A structured clinical output is released through the agreed interface.
Illustrative example. Handling evidence helps downstream teams assess the outputs they receive.
Questions & answers
Evaluate data for its intended use.
Use the clinical record and its handling evidence together when assessing an output.
Does passing validation mean a record is suitable for every use?
Suitability depends on the intended use. Review completeness, consistency, provenance, and clinical context alongside conformance checks and the receiving application’s requirements.
What should a team review when a record looks wrong?
Start with the source record, validation results, terminology mappings, and processing history. That evidence helps identify whether the issue needs source correction, mapping review, or message remediation.
See how trust becomes operational in LYNQSYS.
Explore the platform or talk with Interstella about where quality, governance, and evidence fit in your environment.