This page describes how departments implement 3D ultrasound reconstruction and what the resulting clinical documentation looks like.
Two ways departments implement 3D reconstruction
The meaningful difference between 3D ultrasound implementations is not the clinical indication. It is where the reconstruction runs and how the interpreting physician is involved while it runs. Departments generally fall into one of two patterns.
Reconstruction on a separate workstation
The sonographer acquires the volume. The dataset moves to a workstation that is separate from the ultrasound system. The interpreting physician is present and directing the reconstruction while it is performed, adjusting the rendering, moving through planes, and deciding what the volume needs to show in order to answer the clinical question.
This pattern requires:
- A workstation genuinely separate from the acquisition system
- Software the physician can drive in real time
- Physician availability at the moment reconstruction is performed
- Validated data transfer with PACS/RIS integration
- A report in which the reconstruction findings are actually stated
Reconstruction on the ultrasound system or an integrated PC
The sonographer acquires the volume and reconstruction runs on the ultrasound system itself, or on a PC integrated with it. The physician supervises the reconstruction and interprets the result, without a separate workstation or an additional transfer step. Supervision applies to both codes; what differs is where the reconstruction runs, and the record should reflect what was actually done.
Why the distinction matters clinically
The two patterns differ in where the reconstruction runs. Which pattern your department is running is a question about your equipment and your workflow, not about the patient in front of you.
PIUR recommends answering that question first, with your applications specialist and your IT team, as code selection follows from the workflow and the documentation.
Two Category I codes are commonly discussed in connection with this work: 76376 and 76377. They are not interchangeable, and neither one is the default. Which of them corresponds to a given department’s practice depends on the setup described above and on the record that setup produces. That determination belongs to your coding and compliance teams, working from the AMA’s current descriptors.
Sources: American Medical Association, CPT® (Current Procedural Terminology), for current official descriptors via the CPT Professional Edition and AMA-licensed coding resources; Centers for Medicare & Medicaid Services, Physician Fee Schedule Look-Up Tool.
Documentation that reflects the work performed
Whichever pattern a department runs, the record should allow a reader to reconstruct what actually happened:
- Clinical indication for the examination, and for volumetric imaging specifically
- Equipment and software used, including where reconstruction was performed
- Who performed each step, and the physician’s role during reconstruction
- Findings from the base examination
- Findings derived from the reconstructed volume, stated distinctly
- Clinical impression, and how the volumetric data contributed to it
- Interpreting physician’s signature and credentials
Note: A useful internal test: if the impression would read identically without the reconstruction, then the reconstruction has not been documented as a distinct service.
Where PIUR IMAGING fits
PIUR IMAGING offers tomographic 3D ultrasound in two deployment forms, and departments choose between them on clinical and operational grounds.
PIUR tUS Infinity performs tomographic 3D reconstruction from freehand ultrasound acquisitions on its own workstation, within the indications of its FDA clearances.
PIUR tUS inside is available on GE HealthCare’s LOGIQ™ Open Platform Technology as a hosted application on LOGIQ™ E10, LOGIQ™ E10s, and LOGIQ Fortis™ systems, enabling 3D acquisition and analysis directly on the ultrasound platform. Contact your local GE HealthCare sales representative for availability.
Note: Deployment configuration is a technical fact about our solutions. Whether the record supports a distinct reconstruction service is determined at your site, not by PIUR. Two departments running the same configuration can produce materially different records.
PIUR can describe what our systems do and how they are deployed in your environment. We do not advise on code selection, and we do not provide billing support, appeals assistance, or any assurance regarding payment.