Most ultrasound integrations succeed at the easy half of the problem.

The RealityThe pictures move. The numbers usually do not.

⚠️

The Problem

Numbers arrive as pictures.

Measurements captured on the machine, rendered into a report image, and retyped by hand if they are needed again.

🔧

The Solution

Move the measurements as data.

Structured report content alongside the images, mapped into fields the record can trend.

✅

The Resolution

A growth curve that builds itself.

Serial comparison without transcription, and a written report that satisfies the requirement.

What the standard already defines for structured measurements

The mechanism exists and is more specific than most integration conversations assume.

DICOM describes itself as the standard for the communication and management of medical imaging information and related data, addressing the exchange of digital information between medical imaging equipment and other systems. It is developed by the DICOM Standards Committee, an independent international standards development organisation; the National Electrical Manufacturers Association and its Medical Imaging and Technology Alliance division act as Secretariat. Describing it as maintained by NEMA is a common misattribution.

The standard’s content mapping resource defines a set of obstetric and gynaecological report templates: patient characteristics, procedure summary, fetal biometry, fetal biometry ratios, fetal long bones, fetal cranium, fetal biophysical profile, amniotic sac, early gestation, ovaries, follicles, pelvis and uterus, two vascular measurement groups, and the fetal anatomy survey. Fifteen named templates, each a defined place for a measurement to live as data.

So the answer to “can the measurements travel structured” is that the standard has assumed they would for years. Whether your machine emits them and your record accepts them is a procurement and configuration question, not a standards gap.

The written report, and what CMS actually requires

One obligation underpins all of this and it is shorter than people expect.

The Medicare Claims Processing Manual, Chapter 13 states for the professional component that the interpretation of a diagnostic procedure includes a written report. The report is part of the interpretation, not an optional artifact of it.

Nothing in that requires structure. What structure does is let the same document serve the clinician who reads it once and the systems that need one value out of it repeatedly. Both readers are legitimate and only one of them is served by prose.

Coverage indications, and a policy worth reading with its date

There is a national coverage determination here, and reading it is more useful than reading a summary of it.

CMS’s national coverage determination on ultrasound diagnostic procedures lists covered obstetric indications including pregnancy diagnosis, fetal age determination by biparietal diameter, fetal growth rate, placenta localisation, complete pregnancy sonography, molar and ectopic pregnancy diagnosis, and amniocentesis by ultrasonic guidance.

It also sets three denial reasons plainly: failure to provide documentation of the medical necessity of tests may result in denial; tests for screening purposes performed in the absence of signs, symptoms, complaints or personal history of disease or injury are not covered except as explicitly authorised by statute; and tests not ordered by a treating physician or other qualified treating non-physician practitioner acting within the scope of their licence will be denied as not reasonable and necessary. Uses not listed are left to local contractor discretion.

That determination is from 2007 and still references ICD-9-CM. It remains current policy, and knowing its age is part of reading it correctly.

Acoustic output, and a rule that does not exist

This one is worth correcting because the wrong version circulates widely.

FDA’s ultrasound imaging page states that the principles of As Low As Reasonably Achievable should be practised by health care providers, that ultrasound energy has the potential to produce biological effects including slight tissue heating and cavitation, and that the use of ultrasound solely for non-medical purposes such as keepsake fetal videos has been discouraged.

It also states that there are no federal radiation safety performance standards for diagnostic ultrasound. The thermal index and mechanical index limits that get quoted as though they were a performance standard are premarket clearance limits set out in FDA guidance for marketing diagnostic ultrasound systems, where the global maximum derated spatial-peak temporal-average intensity for fetal imaging is set at 94 milliwatts per square centimetre. That is a limit a manufacturer meets to market a device, not a rule a practice complies with.

The practical consequence for documentation is small but real: if your report template records thermal and mechanical index values, it is recording something useful for ALARA practice, and it is not evidencing compliance with a federal standard, because there is not one.

Image exchange, and where projects actually stall

The common failure is not technical capability but the assumption that one side implies the other.

Ask the ultrasound vendor whether the machine emits a structured report and in which template set. Ask the record vendor whether it consumes structured report content and into which discrete fields. Those are separate questions with separate answers, and a yes to the first with a no to the second produces an integration that moves images beautifully and leaves every measurement to be retyped.

Where the two do not meet, an interface layer between them is the usual answer, and that is ordinary work rather than a bespoke build. It sits with our interface engine and the wider EHR workflow optimization conversation.

• Ask both vendors separately. Emits and consumes are different questions.
• Map to fields, not to a document. A PDF in the chart is not integration.
• Record the indication as data. It is what a denial turns on.
• Know the NCD’s age. 2007, ICD-9-CM, still current.

Qventive provides OB ultrasound EHR integration services for New Jersey practices, normally within IT support for OB-GYN practices rather than as a standalone project.

Where integration touches system configuration, that work runs through OB-GYN EHR and IT support, and every route images or measurements take belongs in your HIPAA risk analysis.

Ultrasound integration: common questions