Identify the view used for the reported interpretation
A digital radiography report may refer to an original image record, a processed analysis view and a compressed picture prepared for communication. Those records can show the same component while retaining different information. Give the interpretation view a clear reference and connect it to the source image. State which view supports the reported finding and which images are merely illustrations. The recipient should not have to guess whether a picture in a presentation is the exact view used for the technical decision.
This guide organizes image-processing provenance after acquisition. It does not prescribe filters, approve interpretation conditions or establish radiographic acceptance criteria. The responsible technical process supplies the actual interpretation and the permitted processing basis. The worksheet records those relationships so they survive export, report preparation and handover. If the source image or analysis state is missing, retain that limitation instead of assuming that the most recent picture in the folder must be the controlling evidence.
Preserve the source image and acquisition event
Record the stable image identifier, component reference and acquisition event before describing processing. A filename alone may be reused or changed during transfer. Preserve the identifiers available through the actual imaging system and the package relationship needed by the recipient. If several source images contribute to a composite or comparison, list their individual references. Do not describe a combined presentation as a single original exposure unless that is what the source record actually establishes.
Keep acquisition metadata separate from later editing or export information. The date a picture was saved for the report does not necessarily identify when the examination occurred. Similarly, the user who exported a view may not be the person who acquired or interpreted the image. Record the roles and events accurately through the actual source documentation. This prevents a convenient file timestamp or author field from becoming a misleading statement about the physical examination or the responsibility for its technical conclusion.
Separate image operations from display choices
Use the terminology of the actual software and distinguish operations that affect the stored image representation from settings used to display it. A selected window, contrast treatment, filter or orientation can change what the recipient sees, but the exact behavior depends on the system. Do not assume all products save those actions in the same way. Preserve the relevant operation record or analysis-session reference and describe what was actually retained with the delivered image.
DÜRR NDT’s D-Tect X documentation describes an image-operation history and saved presets. That is a specific product capability, not a guarantee about every exported file or another viewer. The reporting lesson is to reference the actual history used for the interpretation and check what the recipient receives. A screenshot of the final appearance does not automatically preserve the sequence of operations or the ability to inspect the underlying image state.
Record the processing selection at the time of interpretation
Identify the analysis session or saved state that supports the reported result. If the interpreter considered several views, explain the relevant relationship through the actual review record. Do not replace that history with a generic enhanced image label. Such a label gives the recipient no way to understand which treatment was used or whether the picture was later changed for presentation. A concise reference to a retained processing record can be more useful than a long unverified list of settings.
Carestream’s INDUSTREX software description identifies display filters and appearance settings for image workflows. These features illustrate why the source image and the selected presentation should be distinguishable. Their availability does not prove that a specific filter was appropriate for a particular examination. Keep the actual technical basis and interpretation evidence, and avoid claiming that a manufacturer’s software capability independently establishes the validity of the reported result.
Keep crop boundaries visible in the evidence relationship
A crop can help a reader focus on an indication, but it also removes surrounding context from the selected picture. Record the source image and the cropped region’s physical or image-coordinate relationship where needed. Do not present a crop as proof of the full examination extent. If the interpretation considered the complete source image, preserve that reference separately from the illustration. The recipient should understand what has been omitted from the view rather than assuming that the visible rectangle represents everything examined.
Retain identification and orientation information that helps locate the selected region. If labels or relevant markers fall outside the crop, reference them through the source record instead of adding an unsupported replacement. Cropping for readability must not conceal a material limitation or another feature needed to understand the conclusion. The responsible technical review determines what information belongs in the interpretation record; the report preparer should preserve that decision when choosing the image used for communication.
Distinguish annotations from image evidence
Arrows, circles and text labels are explanatory additions. Identify their purpose and keep them connected to the reviewed interpretation. An annotation can point to a feature without proving its nature, size or acceptability. Do not let a label entered during report formatting become a new technical diagnosis. Where an annotation is supplied by the interpreter, preserve its reference and meaning. Where it is only a discussion marker, say so rather than making it look like a final evaluated finding.
Check whether annotations are stored separately, included in the exported picture or omitted by the recipient’s viewer. The behavior depends on the actual software and export process. A view that looked complete on the preparer’s screen may lose its explanatory layer elsewhere. Conversely, a flattened picture may make the annotations inseparable from the displayed image. Describe the delivered form accurately and retain the underlying source relationship so the recipient can distinguish the examination evidence from the presentation added to explain it.
Preserve orientation and measurement references
Rotating or mirroring a view for layout can change the reader’s understanding of location. Record the actual orientation relationship and preserve the physical datum used in the interpretation. Do not assume that a left-to-right display direction corresponds to the project’s weld direction. If a report image is rotated after analysis, verify that the caption, markers and coordinate references remain correct. A visually tidy page is not useful if the recipient cannot relate the indicated feature to the physical component.
Keep any reported measurement attached to its reviewed analysis basis. A displayed ruler or pixel distance does not by itself establish a physical dimension for the component. Preserve the applicable calibration or reference relationship supplied by the technical record, including units and qualifications. The worksheet does not perform image metrology or validate dimensional measurements. It ensures that a number copied into the report remains connected to the actual image state and the responsible interpretation from which it was obtained.
Worked example: a cropped export loses its source context
In a fictional review, image I-12 is interpreted in a saved session with a defined display treatment and an annotated area of interest. The report preparer exports a cropped picture named weld-final and omits the source identifier and orientation markers. A recipient later asks whether the picture covers the entire weld. The image itself cannot answer that question because it was prepared only to illustrate one reviewed feature. The missing relationship is a reporting problem, not evidence that the whole examination was incomplete.
The revised record links view V3 to I-12 and the actual interpretation session. It identifies the crop’s purpose, the relevant location reference and the external source package. The report keeps the overall examination scope tied to the appropriate technical record. This scenario is hypothetical and sets no image-processing rule or acceptance threshold. It shows why a communication export needs its own provenance even when the underlying examination and interpretation were properly documented elsewhere.
| Record | Purpose | Reference to retain | Assumption to avoid |
|---|---|---|---|
| Source I-12 | Underlying acquisition record | Image identity and examination event | Report export timestamp is the examination date |
| Saved interpretation state | Context used for the technical result | Actual processing and review reference | Any enhanced view represents the same analysis |
| Cropped view V3 | Illustrates one reviewed feature | I-12, crop location and orientation | Visible rectangle proves complete coverage |
| Annotated report picture | Communicates the reviewed finding | Annotation meaning and source relationship | An arrow itself establishes a defect classification |
Review presets and batch operations as actual applied history
A preset name can be a useful shortcut, but it may not fully explain the operations applied to the reported image. Retain the relevant preset version or actual saved operation history where the project requires it. Do not assume that every image in a batch received identical processing simply because it passed through the same workflow. A user may have adjusted an individual image, excluded an operation or changed the preset before the final interpretation.
If a batch action was applied after interpretation for presentation purposes, keep that distinction visible. The resulting pictures may be convenient for a report package without representing the exact analysis states used for the decisions. The responsible reviewer determines whether the presentation remains suitable for its intended purpose. The report preparer should not describe a global export operation as technical re-evaluation or imply that the use of a saved preset proves consistent image suitability across different components and acquisition conditions.
Keep conversion and compression separate from interpretation
Record when the delivered image is a derivative export rather than the original retained image record. Conversion can change file structure, metadata or the information available to a viewer, depending on the format and settings. Do not promise equivalence without the actual technical basis. Identify the intended use of the derivative, such as report illustration or client review under an agreed process, and preserve the relationship to the source retained in the imaging system or technical archive.
The DICONDE handover guide addresses broader exchange and procurement questions. This worksheet focuses on the processing history behind a particular reported view. Keep those scopes distinct. A file-format label does not by itself explain which processing state was used for interpretation, whether an annotation layer is included or what the recipient can reproduce. Test the actual delivered package and document its supported behavior rather than relying on a general interoperability claim.
Identify the software environment used for the result
Record the analysis software and version where required, along with the relevant saved-state reference. If acquisition and interpretation occurred on different systems, preserve that relationship. A product name alone does not establish the exact environment used for the reported decision. Avoid copying the latest advertised version into an old examination record. Use the actual source information, and distinguish any later reanalysis performed after a software change from the original interpretation event.
When a recipient opens the image in a different viewer, check what is available rather than assuming that all processing history transfers automatically. The source data may be readable while a proprietary saved view is not reproduced. State the actual delivery arrangement and any reviewed limitation. This does not mean every handover requires identical software; it means the report should describe what the chosen exchange process preserves and what remains available only through the original analysis record.
Organize the provenance record in the free report tool
Use the digital reporting workspace for the processing-reference table, interpretation summary and explanatory notes. Supported DOCX and XLSX imports can bring in reviewed tabular records after preview. The application does not load DICONDE radiographs, apply image filters or validate the analysis. Its image controls are company and client logo fields. Keep examination images in the agreed external package and use clear text references rather than implying that the report contains or processes the native image data.
The equipment tracker can organize detector or scanner records, and the procedure draft workspace can help structure proposed reporting responsibilities for review. These supporting records do not establish the actual processing state of an individual image. Preserve event-specific evidence and the responsible technical decision. A good report combines a concise, readable result with enough provenance to locate the original image and understand the analysis context behind the selected presentation.
Check the delivered view against the interpretation record
Compare the actual export with the saved interpretation reference. Check identity, orientation, crop, annotations and the stated purpose of the view. Confirm that measurements and captions still refer to the correct feature after layout changes. If the exported appearance differs materially from the reviewed view, obtain the appropriate technical decision rather than assuming the difference is cosmetic. This is particularly useful when a report designer or coordinator prepares the final package from images supplied by another person.
Then open the package from the recipient’s starting point and follow one report reference back to the intended source. Verify the filenames, revision relationships and access arrangement. The buyer-review guide covers wider handover checks. Here the success test is whether the recipient can distinguish acquisition evidence, interpretation context and a communication picture without confusing one for another or relying on an undocumented explanation from the original analyst.
Preserve later processing and interpretation changes
A later review may use a different display treatment on the same source image or reach a revised interpretation. Record which change occurred and what it affects. Do not replace an earlier report picture silently if the associated conclusion or measurement changes. Follow the project’s amendment process and retain the actual review relationship. A new exported image does not necessarily mean new acquisition, and a new interpretation does not automatically mean that the underlying source image has changed.
Use the worksheet to connect image identity, analysis state, selected export and reported result. Replace the fictional example with actual evidence references and keep the table with the delivery package. Its practical value is continuity: another qualified reviewer can understand the result after images have been copied, reformatted or reopened in a later software environment. The record supports that review without claiming that the reporting application interprets radiographs, guarantees authenticity or provides technical approval.
Digital radiography interpretation-view provenance
Download this editable CSV for the task described above. Replace illustrative prompts with your own supported facts. The worksheet is a planning aid; it does not establish inspection acceptance or approval.
Download the free workflow worksheetQuestions about this workflow
Is a report screenshot the original digital radiograph?
Not necessarily. Identify whether it is the source record, a processed analysis view or a derivative picture prepared for communication.
Does a preset name fully describe the processing used?
It may not. Preserve the actual applied history or saved-state reference where needed, including individual changes and the relevant version.
Can I rotate or crop a picture for the report?
Follow the actual reviewed process and preserve identity, location, orientation and the crop’s purpose. Do not imply the selected picture proves the full examination extent.
Does NDT Connect analyze DICONDE images or apply filters?
No. It organizes supplied text and supported Office tables. Image analysis, source retention and technical interpretation remain in the appropriate external workflow.
Sources and editorial scope
Primary references support the specific context cited in the guide. Worked examples and suggested workflows are NDT Connect editorial guidance. Confirm the documents and authority applicable to the actual assignment.
More guides: method-specific report workpapers
- Explain ECA Channel and Surface Maps in Reports
An ECA color map needs a physical reference and a defined signal meaning. Explain how the selected channels and scan coordinates relate to the component before using the image to communicate a location or examination scope.
- Reconcile Tube Inspection Analyst Summaries
A consistent final tube map requires more than merging spreadsheets. Establish a common tube identity, retain each analyst’s actual evaluation and record the responsible decision that resolves every material difference.
- Track Guided-Wave Screening Indications to Follow-Up
A screening indication and a local examination result answer different questions. Keep both records linked without converting the screening output into a local minimum-thickness value or treating a completed work order as technical closure.
- Record MT Examination Coverage and Sequence References
A statement that MT was performed should identify the actual examined surfaces and the arrangement supporting that scope. Preserve executed coverage, sequence references and limitations without prescribing a generic magnetizing technique.
