DICOM Attribute

Manufacturer's Model Name (0008,1090)

Keyword
ManufacturerModelName
VR
LO
VM
1

Definition

Manufacturer's model name of the equipment that produced the Composite Instances.

From NEMA PS3.3 §C.7.5.1.

Attribute Metadata

Tag
(0008,1090)
Keyword
ManufacturerModelName
Name
Manufacturer's Model Name
Value Representation (VR)
LO
Value Multiplicity (VM)
1
Status
Active
Source
NEMA PS3.6 (table_6-1)

This attribute is part of the current DICOM Standard. Its value representation is LO with multiplicity 1.

Used in 9 Modules

This attribute uses the LO Value Representation. Multiplicity 1 governs how many values may be encoded.

Integration Notes

Real-world integration guidance for engineers implementing this attribute in Mirth Connect, FHIR gateways, HL7 v2 bridges, and cloud DICOM services. Authoritative source data where available; reference examples and operational notes where they add value.

FHIR Mapping

No direct FHIR ImagingStudy mapping published for this attribute. Some tags map indirectly via the Patient, Endpoint, or ImagingSelection resources — Phase 2b will expand coverage to those.

HL7 v2 Equivalent

  • n/a (no HL7 v2 equivalent)

    ManufacturerModelName is a modality-side attribute; not conveyed in HL7 v2 messages.

    Source: common convention

Verify against IHE Radiology TF Vol 2 and your facility's interface specification before production use.

Cloud DICOM Support

  • AWS HealthImaging Preserved
  • Azure DICOM Preserved
  • Google Cloud Healthcare Preserved

Manufacturer Model Name — preserved by all three. Used in vendor-specific viewer behavior.

Per-vendor source URLs and verification date in src/content/dicom/cloud-support.json#_meta. Status taxonomy: required (mandated on Store), queryable (QIDO-RS matching key), preserved (stored as-is), promoted (AWS top-level metadata), unsupported (stripped/rejected).

Real-World Sample Values

  • RHAPSODE CT_small.dcm
  • MRT50H1 MR_small.dcm
  • LOGIQ 700 ExplVR_BigEnd.dcm

Extracted from pydicom test fixtures (MIT, de-identified).

Mirth Connect Example

Manufacturer Model Name → equipment registry lookup — Cross-reference the modality model against an internal registry to pull asset ta

Cross-reference the modality model against an internal registry to pull asset tag, calibration date, etc.

// (0008,1090) Manufacturer's Model Name — look up against asset registry
var model = String(msg.dataset.attr.(@tag == '00081090').value).trim();
var mfr   = String(msg.dataset.attr.(@tag == '00080070').value).trim();
var registryKey = (mfr + '|' + model).toUpperCase();
// Mirth Database Reader pattern — query asset DB by composite key
var dbConn = DatabaseConnectionFactory.createDatabaseConnection(
  'org.postgresql.Driver',
  configurationMap.get('ASSET_DB_URL'),
  configurationMap.get('ASSET_DB_USER'),
  configurationMap.get('ASSET_DB_PASS')
);
try {
  var rs = dbConn.executeCachedQuery('SELECT asset_tag FROM equipment WHERE registry_key = ?', [registryKey]);
  if (rs.next()) channelMap.put('asset_tag', rs.getString('asset_tag'));
} finally { dbConn.close(); }

Reference only — validate before production. Snippets are starting points, not turnkey solutions. Always test against your channel's specific message structure and your facility's interface specification. See Mirth Connect User Guide + NEMA PS3.6 + your vendor conformance statement for authoritative specification.

Common Operational Errors

Operational error patterns for the most-queried tags will be added as coverage expands.

DICOM Integration Services

Saga IT builds production DICOM integrations across Mirth Connect, FHIR gateways, and cloud imaging platforms. If you're working with ManufacturerModelName or the broader (0008,1090) context: