Skip to main content

Unfamiliar Lab Result Flags: Preserve the Source and Resolve the Meaning

An unfamiliar laboratory result flag should remain explicitly unresolved until its meaning is clarified. Preserve the original value, units, reference information, source flag and report version; do not silently translate an unsupported code into “normal”. Technical mapping and clinical interpretation are separate decisions. A doctor may need to assess the patient before the interface problem is resolved, so a mapping issue must have a clinical escalation route as well as a software correction process.

By Bractis · Updated · 15 min read

Indian clinics receiving electronic laboratory results, imported spreadsheets or reports with unfamiliar symbols and flags.

Distinguish the result, its flag, its status and its clinical meaning

A numerical result is the reported measurement. An interpretation flag is the laboratory’s categorical annotation. A report status describes whether information is preliminary, final or amended. The clinician’s assessment considers the patient and the available evidence. These concepts should not collapse into one green or red badge.

HL7 FHIR R4 separates an observation value, interpretation, reference range and a reason for an absent value. This illustrates why an unrecognised interpretation code is not the same problem as a missing numerical result. The R4 data model is a versioned technical reference, not a universal dictionary for every laboratory interface.

If a source sends an unfamiliar symbol beside a legible number, the number may still be visible while the symbol remains unexplained. If the source sends no number because analysis failed, inventing a zero is a different error. Give each uncertainty its own wording and next action.

Source: HL7 FHIR R4: Observation definitions

Keep the laboratory’s wording available beside the imported display

The receiving clinic needs enough provenance to compare its display with the originating report: laboratory, accession or report reference, specimen or observation time, issue time and version. Retain the literal flag as received, including punctuation, and the source document or message where available.

An interface may use a local code that resembles a familiar abbreviation but has another meaning. Do not infer that “A”, an asterisk or an exclamation mark means the same thing across providers. The laboratory’s documented code definitions and the agreed interface mapping are the place to resolve it.

Keep the original and interpreted values distinguishable. If the clinic later maps a source code to a display label, the record should still show what the laboratory supplied and which mapping version produced the label. That history becomes important when investigating an earlier decision.

Worked provider-code case: the same characters can require a different decision

Fictional case L-28 involves an Indian clinic receiving reports from two independent laboratories. Lab A’s local flag dictionary A3 defines X2 as “specimen qualification: read the source comment”. Lab B’s dictionary B1 uses the same characters for “method note: read the source comment”. These meanings are invented for this exercise, not real laboratory codes. A clinic-wide replacement of every X2 with one label would erase the difference between the sources.

For one Lab A result, the source value is 18, the unit is U and the printed interval is 5–20. Those are also fictional. The value lies inside that displayed interval, but that arithmetic says nothing about the qualification described by X2. Preserve the number, unit, interval, literal flag and source comment as separate information. A specimen-related qualification does not itself prescribe recollection, establish invalidity or select treatment; the laboratory clarification and clinical assessment determine the relevant next action.

There are three different version questions. A3 identifies the laboratory’s code dictionary. Report version 2 identifies a later version of a particular result. M8, used below, identifies a proposed clinic display-mapping revision. A newer report can still use dictionary A3, and changing M8 does not create a laboratory amendment. Where the incoming source does not identify its dictionary, obtain an evidenced interpretation of the applicable feed rather than guessing from its receipt date.

FHIR R4’s Coding definition distinguishes the code system, its version, the code and its displayed meaning. It is a useful technical distinction, not proof that these fictional laboratory feeds use FHIR or that every laboratory sends a version field. The following five input cases are proposed evaluation cases, not observed Bractis test results.

On a narrow screen, scroll the table horizontally to read all columns.

Fictional L-28 mapping scope: five inputs that must not share a fallback
Source contextAvailable informationScoped display decision
Lab A / dictionary A3 / X218 U; interval 5–20; source qualification comment availableRetain the value and interval; describe the confirmed qualification and keep its comment accessible
Lab A / dictionary A3 / X2, no valueSource says measurement not completedPreserve the absent value and source reason; knowing X2 does not create a result or zero
Lab A / dictionary A4 / X2No confirmed A4 definition in this exerciseKeep meaning unresolved; do not automatically carry the A3 definition forward
Lab B / dictionary B1 / X2Separate confirmed method-note definitionUse B’s documented meaning; the A3 qualification label does not apply
Lab A / dictionary A3 / !X2Different literal code with no confirmed definitionPreserve the exclamation mark and unresolved code; do not strip it to force a match

Source: HL7 FHIR R4: Coding definitions

Give unresolved states different actions

A generic “invalid result” banner tells staff too little. The following classification is an original triage aid for information problems. It does not rank clinical urgency; the responsible clinician determines that using the patient’s situation and available information.

Make uncertainty readable in text, including on a printout. Colour alone is inadequate, and a blank flag column can be mistaken for reassurance. A useful message says what is unknown, where the original can be found and who is resolving the issue.

On a narrow screen, scroll the table horizontally to read all columns.

Information problems that should not be treated as normal results
Observed issueWhat remains knownAppropriate resolution route
Unrecognised source flagOriginal value and flag may be availableLaboratory clarifies meaning; interface owner verifies mapping
Missing reference informationReported value and units may be intactObtain the applicable source information; clinician assesses context
Missing or failed measurementA test was requested, but no usable value is suppliedPreserve the reason and obtain the laboratory’s next-step advice
Conflicting source and imported displayTwo representations disagreeShow the source, contain misleading output and investigate conversion
Preliminary or amended reportA versioned result existsIdentify current version and route material changes for review

Separate immediate clinical assessment from technical repair

A reception team discovering an unfamiliar flag should tell the responsible clinician what is available and what is uncertain. A technical support ticket is not a clinical handover. If a laboratory has communicated a critical concern, retain that communication and use the clinic’s established clinical escalation arrangement.

The doctor may contact the laboratory, assess the patient or arrange an alternative investigation. Record that decision independently of whether the software mapping has been repaired. Conversely, completing a mapping task should not automatically mark a result clinically reviewed.

An unavailable doctor needs accepted cover. A queue assigned to an absent clinician can look orderly while nothing happens. Handover should identify the unresolved flag, the source report and any action already taken, so the next clinician does not start from an unexplained badge.

Require evidence for a mapping change

A defensible mapping record links the provider and code to its documented meaning, source confirmation, intended display and reviewer. Include the interface or catalogue version where relevant. Do not make a global change because one result happened to look plausible.

Before applying the mapping more widely, test representative messages with that code, including missing values, textual results and amended reports if supported. A rule that works for a numerical observation may mislabel a qualitative result. Test both the interactive view and exported summaries.

Review earlier results when the old mapping was misleading

Fixing future messages is only part of the work if earlier results were shown as normal. Identify the affected provider, code, period and output surfaces. The search should include downloaded visit summaries and referrals where the misleading interpretation may have been copied.

A qualified clinician decides which cases need reassessment or communication. Preserve the earlier representation and record the correction; do not silently rewrite history so it appears the accurate flag was always present. The patient record needs the consequences of the correction, not just a software deployment note.

Keep the investigation bounded by evidence. If the defect affected one laboratory feed, do not claim every result from every source is wrong. Equally, do not assume a single discovered example was the only affected record without examining the relevant input history.

Reconcile message deliveries, result versions and records needing review

Suppose L-28’s old mapping M7 displayed Lab A/A3/X2 as normal during a defined review window. The fictional message log contains nine deliveries. Six match that exact scope. The other three are one Lab B/B1/X2 delivery, one Lab A/A4/X2 delivery and one Lab A/A3/!X2 delivery. Excluding them from this particular repair does not establish that their displays are correct; each still needs the interpretation appropriate to its own evidence.

The six matching deliveries represent four distinct source-result versions across three result records, R1, R2 and R3. Two deliveries are retries of the same versions. Preserve the delivery log, but do not count a retry as a new measurement or open a duplicate clinical task merely because transport repeated. Conversely, R1 version 2 is a genuine source amendment and must not disappear during deduplication. The table gives the assumed identities for this exercise; real deduplication requires reliable source identifiers and comparison.

This produces different work lists: four versioned displays to inspect, three current result records requiring an accountable clinical review decision, and two known exported documents requiring impact assessment. One export used R1 version 1 and the other R2 version 1. They remain relevant even if the current screen now uses the corrected mapping. The technical owner must preserve evidence of what each earlier output displayed; the responsible clinician determines any necessary patient or recipient correction.

On a narrow screen, scroll the table horizontally to read all columns.

L-28 historical scope: six deliveries, four versions and three result records
Result versionDeliveriesCurrent relationshipKnown copied output
R1 / version 12: original plus retrySuperseded by R1 version 2One exported visit summary used this version
R1 / version 21Current amended version of R1No additional copied output identified in this example
R2 / version 11Current version of R2One exported referral used this version
R3 / version 12: original plus retryCurrent version of R3No copied output identified in this example

Explain uncertainty without sending a diagnosis in a notification

A patient-facing message can say that a report needs a doctor’s review or that the clinic is clarifying a reporting detail. It should not translate an unknown flag into “all normal” or an alarming diagnosis. Discuss the appropriate wording with the responsible clinician.

For patients using a shared family phone, confirm the intended recipient and channel before sending details. A short appointment or contact message can avoid exposing sensitive interpretation in a lock-screen preview. This communication choice does not replace the clinical response if the situation requires prompt action.

Close the mapping task only on its evidence and keep the clinical work visible

For the L-28 handover, assume M8 is a proposed replacement rule whose application has not yet been approved or demonstrated. Its acceptance checks must include preserving source values, units, intervals, comments and amendment relationships; keeping unknown contexts unresolved; and inspecting the relevant screen and export. A technical reviewer should compare these outputs before accepting a historical redisplay. Do not mark the plan “deployed” merely because the laboratory supplied a code definition.

At the fictional 28 October cutoff, a clinician has documented review of current R1 version 2, a covering clinician has accepted R2 but has not yet recorded its review, and R3 still lacks accepted clinical ownership. Thus one of three current records has a documented review and two remain open. This is workflow accounting, not a statement that one patient is safe or that the others have abnormal results. The actual clinical decisions are deliberately not invented here.

Both known exports remain on the impact list. The R1 review does not by itself establish that the earlier visit summary needs no correction, that the recipient has been reached, or that the patient understood any changed explanation. Assign those decisions and communications explicitly. Where a family phone is used, the patient-contact task should preserve the authorised recipient and avoid placing an unexplained flag or diagnosis in a general notification.

The record below distinguishes laboratory meaning, proposed technical work and clinical follow-through. If a later review finds another affected source period or output, expand the recorded scope with the reason. Do not quietly widen a provider-specific rule while continuing to report the earlier bounded counts as though they describe the larger investigation.

Test unsupported values deliberately during software evaluation

Use fictional reports containing a known flag, an unknown flag, an absent value and a corrected result. Observe whether the system preserves the source and labels uncertainty. A demonstration using only familiar high and low values will not expose the fallback behaviour.

Then ask what happens after the unknown code is mapped. Can the clinic identify which earlier records used the old rule? Can clinical review remain outstanding after the technical task closes? These questions reveal whether the system supports investigation and accountability, rather than merely displaying attractive results.

Worked example: the dangerous default in a fictional feed

A fictional laboratory sends value 18, units U, reference text 5–20 and local flag “X2”. The number’s position inside that displayed interval does not establish what X2 means. The clinic initially cannot interpret the flag, so it retains the source and shows “source flag requires clarification”. The laboratory explains that X2 concerns a specimen qualification, not a high/low classification. A scoped mapping can now describe that qualification. The clinician separately decides how it affects the patient’s assessment. This is an invented information-flow example, not a real test or clinical threshold.

Unfamiliar Laboratory Flag Resolution Worksheet

Use these prompts in your clinic’s own notes. Record the result, responsible person and next action for each item.

Original evidence
Can staff retrieve the exact source flag, units, report version and applicable reference text?
Clinical owner
Who assesses the patient while the code meaning is being clarified?
Mapping evidence
Which laboratory definition supports the proposed label, and how narrowly does the rule apply?
Earlier exposure
Which prior results or exported documents may have shown a misleading interpretation?

Questions doctors ask

Can an unknown lab flag be imported as normal?

An unknown code does not establish a normal interpretation. Preserve the source and make the unresolved meaning explicit until the laboratory and interface owner clarify it. Clinical assessment may still need to proceed meanwhile.

What if the number is inside the printed reference interval?

That does not explain an unfamiliar flag. The flag could concern another qualification or reporting condition. Keep the number and source interval visible, and clarify the flag without inventing its meaning.

Should a missing laboratory value appear as zero?

No. Zero is a value and may be clinically interpreted as one. Record the absence and its source reason, such as analysis not completed, rather than manufacturing a numerical result.

Must the doctor select normal or abnormal to close the screen?

The workflow needs an honest unresolved state and an accountable next action. Forcing a binary choice can create false certainty. The clinical decision and the technical mapping task should be recorded separately.

Does repairing the interface finish the incident?

Only if there is no remaining clinical or historical impact. Determine whether earlier results were misrepresented, have responsible clinicians assess affected cases, and track any necessary corrections or communication.

Can the clinic reuse a flag definition when another laboratory sends the same code?

Only when there is evidence that the relevant code system and meaning are equivalent for that source and context. The same characters alone are insufficient. Retain the provider and definition reference, and keep unconfirmed codes unresolved rather than copying another laboratory’s label.

Should repeated imports create a new clinical review task every time?

First establish whether they are retries of the same source result version or actual new or amended results. Preserve transport history while linking confirmed retries to the same record. A new source amendment still needs its appropriate review; deduplication must not hide a changed result.

Sources and scope

Updated on . This article combines the cited references with Bractis’s original workflow analysis and illustrative examples. Product capabilities depend on the configured scope. No independent clinical or legal review is claimed.

  • HL7 FHIR R4: Observation definitions

    Official version 4.0.1 definitions checked 28 October 2026: value, interpretation, reference information and data absence remain distinct. This is a versioned technical reference, not a claim about current product conformance or a clinical protocol.

  • HL7 FHIR R4: Coding definitions

    Official version 4.0.1 definitions checked 28 October 2026 for system, version, code and display. The fictional provider dictionaries are original examples, not HL7 code assignments or evidence that a particular laboratory uses FHIR.

Try the workflow
with Bractis.

Bring a fictional report with an unsupported flag and inspect the source display, unresolved state, clinical handover and correction history.

Request a clinic demo