A Health Gorilla reconciled chart must preserve conflicting source records

Retain every candidate fact and its context

The direct answer is that reconciliation should produce a selected representation and an inspectable evidence set. Each candidate fact should retain patient-match context, source organization and system, author where available, record and encounter identifiers, original code and text, status, effective and recorded times, units, reference range, negation, correction state, document context, retrieval purpose, access path, and raw or permitted source representation.

Apparent duplicates can differ materially. Two medication records may describe an order and a patient-reported use; two lab values may use different methods or units; an allergy may be active, historical, entered in error, or denied; a diagnosis can be a billing code, problem-list assertion, or ruled-out condition. De-duplication should preserve those distinctions before deciding whether records express the same clinical fact.

Make the reconciliation decision explainable

When values conflict, the record should identify the candidates, normalization and mapping version, precedence rule or model, confidence where used, selected value, unresolved ambiguity, reviewer or override, and time. A newer timestamp may not mean a newer clinical event, and an apparently more authoritative source may have received its value from another exchange path. Provenance should follow the fact through every copy and transformation.

The unified view should distinguish source assertion, normalized representation, reconciliation output, and user interpretation. If a source corrects or retracts a record, the system should identify downstream charts, alerts, measures, and decisions that used the prior value. Recomputing the latest chart is useful, but it should not rewrite what a clinician, care manager, patient, or analytic process saw earlier.

Bound completeness and fitness to the use

A record can be broad and still incomplete for a specific purpose. The response should identify the exchange purpose, requested time range and data classes, participating sources, successful and failed queries, access or consent limits, unavailable endpoints, delayed records, excluded formats, and data cut-off. A completeness label should not imply that every provider, setting, test, medication, or event is represented.

Fitness also changes by use. A reconciled chart used to orient a care coordinator is not automatically sufficient for medication reconciliation, diagnosis, treatment, quality reporting, payment, risk adjustment, research, or patient notice. The receiving workflow should retain intended use, decision owner, review requirements, unresolved gaps, and the original sources needed for confirmation or correction.

Test a duplicate, contradiction, correction, and missing source

A representative evaluation should retrieve the same lab through two paths, send one result in different units, provide conflicting medication and allergy statuses, fail a source query, merge and then unmerge two identities, correct the authoritative record, and trigger an alert from the former value. Reviewers should reconstruct every candidate, match, transformation, reconciliation, access event, downstream use, correction, and remaining gap.

Health Gorilla's official site supports the described discovery, matching, translation, de-duplication, reconciliation, provenance, access-log, network, and alert positioning. It does not establish identity accuracy, source completeness, semantic equivalence, clinical correctness, TEFCA participation for a particular customer, authorization, compliance, interoperability, or outcome. Healthcare organizations and their clinical, health-information, privacy, security, compliance, and legal owners retain responsibility.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

Health Interoperability Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.