한국어

Chapter 8: WIA-MEDICAL-IMAGING Standard

Complete Technical Specification with 4-Phase Implementation Architecture

8.1 Standard Overview

The WIA-MEDICAL-IMAGING standard provides a comprehensive framework for implementing interoperable medical imaging systems. Built on the WIA 4-phase architecture (Data, API, Protocol, Integration), this standard enables seamless connectivity between imaging equipment, PACS, AI algorithms, and clinical systems.

Guided by the principle of 弘益人間 (Hongik Ingan) - "Benefit All Humanity" - this standard aims to make advanced imaging diagnostics accessible globally through standardized, interoperable systems.

4
Architecture Phases
12
Core Data Models
28
API Endpoints
100%
DICOM Compatible

8.2 WIA 4-Phase Architecture

The WIA-MEDICAL-IMAGING standard implements the WIA 4-phase architecture pattern:

Architecture Philosophy

The 4-phase architecture separates concerns into distinct layers: Phase 1 (Data) defines the information model compatible with DICOM; Phase 2 (API) provides programmatic access via DICOMweb and REST; Phase 3 (Protocol) enables messaging and image transfer; Phase 4 (Integration) connects with EHR, AI, and clinical systems.

Phase Name Purpose Components
Phase 1 Data Layer Information modeling Studies, series, instances, reports
Phase 2 API Layer Programmatic access DICOMweb, FHIR ImagingStudy, REST
Phase 3 Protocol Layer Communication DICOM messaging, HL7, image transfer
Phase 4 Integration Layer External connectivity EHR, RIS, AI platforms, enterprise

8.3 Phase 1: Data Layer Specification

The Data Layer defines core information models aligned with DICOM standards:

Core Data Models

ImagingStudy Model

{
  "studyInstanceUID": "string (DICOM UID)",
  "accessionNumber": "string",
  "studyDate": "date (YYYYMMDD)",
  "studyTime": "time (HHMMSS)",
  "studyDescription": "string",
  "modality": ["string (CT|MR|US|CR|MG|PT|NM)"],
  "patient": {
    "patientId": "string",
    "patientName": "string (DICOM PN format)",
    "birthDate": "date",
    "sex": "enum (M|F|O)"
  },
  "referringPhysician": {
    "name": "string",
    "identifier": "string"
  },
  "numberOfSeries": "integer",
  "numberOfInstances": "integer",
  "procedureCodes": [{
    "code": "string",
    "scheme": "string",
    "meaning": "string"
  }],
  "availability": "enum (ONLINE|NEARLINE|OFFLINE)",
  "retrieveURL": "string (DICOMweb endpoint)"
}

ImagingSeries Model

{
  "seriesInstanceUID": "string (DICOM UID)",
  "studyInstanceUID": "string",
  "seriesNumber": "integer",
  "seriesDescription": "string",
  "modality": "string",
  "bodyPartExamined": "string",
  "seriesDate": "date",
  "seriesTime": "time",
  "numberOfInstances": "integer",
  "laterality": "enum (L|R|B)",
  "manufacturer": "string",
  "modelName": "string",
  "stationName": "string",
  "performedProcedure": {
    "code": "string",
    "description": "string"
  }
}

AIResult Model

{
  "resultId": "string (UUID)",
  "studyInstanceUID": "string",
  "algorithmName": "string",
  "algorithmVersion": "string",
  "vendor": "string",
  "analysisType": "enum (detection|classification|segmentation|quantification)",
  "findings": [{
    "findingId": "string",
    "findingCode": { "code": "string", "scheme": "string", "meaning": "string" },
    "probability": "number (0-1)",
    "severity": "enum (normal|mild|moderate|severe)",
    "location": {
      "reference": "seriesInstanceUID:sopInstanceUID",
      "coordinates": { "x": "number", "y": "number", "z": "number" },
      "boundingBox": { "x1": "y1": "x2": "y2" }
    }
  }],
  "processingTime": "number (seconds)",
  "confidence": "number (0-1)",
  "timestamp": "datetime"
}

8.4 Phase 2: API Layer Specification

The API Layer provides programmatic access through DICOMweb and REST endpoints:

API Endpoints Overview

Category Endpoint Method Description
Studies /dicomweb/studies GET QIDO-RS query studies
/dicomweb/studies/{uid} GET WADO-RS retrieve study
/dicomweb/studies POST STOW-RS store study
Series /dicomweb/studies/{uid}/series GET Query series in study
/dicomweb/studies/{uid}/series/{uid} GET Retrieve series
Instances /.../instances GET Query instances
/.../instances/{uid} GET Retrieve instance
AI Analysis /api/v1/ai/analyze POST Submit for AI analysis
/api/v1/ai/results/{id} GET Get analysis results
/api/v1/ai/algorithms GET List available algorithms
Worklist /api/v1/worklist GET Query worklist items
/api/v1/worklist/{id}/status PUT Update item status

Authentication

APIs use OAuth 2.0 with JWT tokens. Scopes include: studies:read, studies:write, ai:analyze, worklist:manage, admin:all. SMART on FHIR enables EHR-launched imaging applications.

8.5 Phase 3: Protocol Layer Specification

The Protocol Layer defines communication standards for image exchange:

Supported Protocols

Protocol Use Case Standard
DICOM DIMSE Traditional image transfer C-STORE, C-FIND, C-MOVE
DICOMweb RESTful image access WADO-RS, STOW-RS, QIDO-RS
HL7 v2 Orders, demographics ORM, ADT messages
FHIR Modern EHR integration ImagingStudy, DiagnosticReport
IHE Profiles Workflow orchestration SWF, XDS-I, PIR

AI Pipeline Message Format

{
  "header": {
    "messageId": "string (UUID)",
    "messageType": "AI_ANALYSIS_REQUEST|AI_ANALYSIS_RESULT",
    "timestamp": "datetime (ISO 8601)",
    "source": { "systemId": "string", "name": "string" },
    "destination": { "systemId": "string", "name": "string" }
  },
  "payload": {
    "studyInstanceUID": "string",
    "algorithm": "string",
    "priority": "enum (STAT|ROUTINE)",
    "parameters": { /* algorithm-specific */ },
    "callbackURL": "string (webhook for results)"
  }
}

8.6 Phase 4: Integration Layer Specification

The Integration Layer connects imaging systems with the healthcare ecosystem:

Integration Patterns

System Integration Method Data Exchanged
EHR FHIR, IHE XDS-I Study references, reports
RIS HL7 v2, DICOM Worklist Orders, scheduling, status
AI Platform REST API, DICOMweb Images, analysis results
Voice Dictation HL7, proprietary Reports, transcriptions
Dose Registry DICOM SR, API Radiation dose reports
Research Platform De-identified export Anonymized datasets

✓ Implementation Best Practices

8.7 Compliance Mapping

The WIA-MEDICAL-IMAGING standard maps to regulatory and industry frameworks:

Framework Standard Elements Coverage
DICOM Data models, protocols Full compliance
IHE Radiology Integration profiles SWF, XDS-I, PIR support
HL7 FHIR ImagingStudy, DiagnosticReport R4 aligned
HIPAA Security, privacy Encryption, access control
FDA SaMD AI integration Audit trails, versioning

8.8 Reference Architecture

Architecture Components

📌 Key Takeaways

📝 Review Questions

  1. Describe the four phases of the WIA architecture and their purpose in medical imaging systems.
  2. How does the ImagingStudy data model relate to DICOM information hierarchy?
  3. Design an API workflow for submitting a CT study for AI analysis and receiving results.
  4. Explain the relationship between DICOMweb services and traditional DICOM DIMSE operations.
  5. How does the Integration Layer connect imaging systems to hospital EHR?
  6. What compliance considerations apply to AI algorithm integration in the WIA framework?

弘益人間 (Hongik Ingan) - Benefit All Humanity

The WIA-MEDICAL-IMAGING standard embodies the principle of benefiting all humanity by democratizing access to advanced imaging diagnostics. Through standardized, interoperable systems, we can bring the power of modern imaging and AI-assisted diagnosis to healthcare facilities worldwide, improving outcomes for patients everywhere.

Chapter 8 — Notes & References

  1. WIA Standards Public Repository (medical-imaging folder), MIT License, GitHub: WIA-Official/wia-standards-public/tree/main/medical-imaging — open standard initiative providing source code for simulator, spec, API, and ebook assets cited throughout this volume; serves as the canonical verification record for all primary-source citations made by the WIA standard committee in this chapter. Canonical ENUM tokens used in this volume include CT, MRI, PET, SPECT, MAMMOGRAPHY, ULTRASOUND, XRAY, DICOM_3_0, NIFTI, NRRD, JPEG_BASELINE, JPEG_2000_LOSSLESS, HEVC, DICOMWEB, QIDO_RS, STOW_RS, WADO_RS, PACS, VNA, RIS, HIS, FDA_510K, CE_MDR, MFDS_CLASS_2, HIPAA, GDPR, DICOM_CONFORMANCE, RUL, RML, RLL, LUL, LLL, MEDIASTINUM, HL7_FHIR_IMAGING, IHE_RAD, NEMA_MITA, DICOM_SR, RADLEX, U_NET, V_NET, RESNET, VIT, TRANSFORMER, CNN, MONAI.

8.9 Simulator ENUM Tokens and Threshold Mapping

This section aligns Chapter 8 integrated-standard content with simulator panels 1-5 at the token level. The ENUMs DICOM_3_0, DICOMWEB, HL7_FHIR_IMAGING, IHE_RAD, NEMA_MITA, DICOM_SR, DICOM_PS3, and RADLEX appear throughout the book in UNDERSCORE notation and map 1:1 with WIA-MEDICAL-IMAGING's four-layer architecture: Data, API, Protocol, and Integration. ENUM tokens serve as common identifiers across NEMA, IHE, HL7, and national-regulator standards documentation.

8.9.1 Standard ENUM Mapping

Table 8.9.1 WIA-MEDICAL-IMAGING standard ENUMs and sections
ENUM TokenStandardPublishing BodyWIA Mapping
DICOM_3_0 / DICOM_PS3DICOM Standard, PS3.xNEMA MITAData and Protocol layers
DICOMWEBDICOMwebNEMA, IHEAPI layer (WADO-RS, STOW-RS, QIDO-RS)
HL7_FHIR_IMAGINGHL7 FHIR ImagingStudyHL7 InternationalIntegration layer (EHR)
IHE_RADIHE Radiology Technical FrameworkIHE InternationalIntegration layer (SWF, XDS-I)
NEMA_MITANEMA Medical Imaging & Technology AllianceNEMADICOM governance
DICOM_SRDICOM Structured ReportNEMAData layer (reports)
RADLEXRadLex Radiology LexiconRSNAData layer (vocabulary)
HL7_FHIR_IMAGING + FDA_510KEHR integration + AI SaMDHL7 + FDAIntegration + certification

8.9.2 PACS and Infrastructure ENUMs

WIA-MEDICAL-IMAGING provides integration standards for the following infrastructure ENUMs: PACS (Picture Archiving and Communication System), VNA (Vendor Neutral Archive), RIS (Radiology Information System), HIS (Hospital Information System), CIS (Clinical Information System), EMR (Electronic Medical Record), and EHR (Electronic Health Record), all connected by the WIA Integration Layer (IHE SWF, XDS-I, HL7, FHIR). DICOM_NODE and AE_TITLE identify DICOM network nodes. Certification ENUMs FDA_510K, CE_MDR, MFDS_CLASS_2, HIPAA, GDPR, and DICOM_CONFORMANCE ensure regional regulatory compliance when applying the integrated standard.

8.10 WIA-MEDICAL-IMAGING Integrated Standard Deep Dive

8.10.1 Four-Layer Architecture Alignment

WIA-MEDICAL-IMAGING comprises four layers: Data (DICOM-aligned ImagingStudy, ImagingSeries, AIResult), API (DICOMweb WADO-RS, STOW-RS, QIDO-RS plus REST), Protocol (DICOM DIMSE plus DICOMweb plus HL7 plus FHIR), and Integration (EHR, RIS, AI, analytics). Each layer aligns with the four-axis governance model for medical imaging information published by national health authorities, providing clear responsibility boundaries across data governance, interoperability, clinical application, and regulatory compliance. NEMA PS3 (Korean edition, published via the Korean Society of Radiology) translates DICOM PS3.1 through PS3.20 in full.

8.10.2 DICOMweb and RESTful Medical Imaging

DICOMweb (NEMA PS3.18) is the RESTful web services layer of DICOM. WADO_RS (Web Access to DICOM Objects RESTful Services) handles image retrieval, STOW_RS (Store Over the Web RESTful Services) handles storage, QIDO_RS (Query based on ID for DICOM Objects RESTful Services) handles queries, and WADO_URI supports single-object URI access. Modern medical imaging viewers (OHIF Viewer, Cornerstone3D) increasingly migrate to DICOMweb-based zero-footprint web viewers, replacing legacy desktop clients. National security guidelines mandate TLS 1.3, OAuth 2.0, and OpenID Connect for DICOMweb traffic.

8.10.3 HL7 FHIR ImagingStudy Integration

HL7 FHIR R4 ImagingStudy resources express patient, image series, DICOM UIDs, and acquisition information in EHR-friendly JSON. The WIA Integration Layer uses FHIR ImagingStudy to bidirectionally synchronize images with EHR systems (Epic, Cerner, OpenMRS, and similar platforms). DiagnosticReport represents radiology reports, while Observation resources express quantitative measurements such as RECIST, BMD, and ejection fraction. National EHR certification programs increasingly require EHR-DICOM integration verified through FHIR conformance.

8.10.4 IHE Radiology Integration Profiles

IHE Radiology Technical Framework provides standard integration profiles for imaging workflow. SWF (Scheduled Workflow) defines the standard RIS-modality-PACS-viewer workflow; XDS-I (Cross-Enterprise Document Sharing for Imaging) supports cross-institutional image sharing; PIR (Patient Information Reconciliation) reconciles patient information; ARI (Access to Radiology Information) enables external system access; MRRT (Management of Radiology Report Templates) governs reporting templates; and AIR (Artificial Intelligence Results) standardizes AI output. The ATNA (Audit Trail and Node Authentication) profile is the standard for security and audit logging.

8.10.5 RadLex and Imaging Vocabulary Standards

RadLex (RSNA Radiology Lexicon) defines over 50,000 radiology terms in a hierarchical structure. The WIA Data Layer applies RadLex codes to DICOM SR (Structured Report) reports, FHIR Observations, and RIS procedure codes, ensuring semantic interoperability. National radiology societies often translate RadLex into local languages and recommend its use in national medical imaging data standardization white papers. Mappings to SNOMED CT, LOINC, and ICD-10-CM are verified through NIST Health IT standards tools.

8.10.6 Security, Privacy, and Audit Trails

WIA-MEDICAL-IMAGING complies with HIPAA, GDPR, and equivalent national personal-information statutes governing sensitive medical data. Security consists of TLS 1.3, OAuth 2.0, OpenID Connect, multi-factor authentication (MFA), and end-to-end encryption (at-rest and in-transit). Audit trails record all image access, modification, deletion, and export events per the IHE ATNA (Audit Trail and Node Authentication) profile. Retention periods commonly span 10 years for imaging records and 5-10 years for clinical reports, depending on jurisdiction. The Office of the National Coordinator for Health IT (ONC) provides additional federation guidance for cross-jurisdictional health IT exchanges.

8.11 Extended Endnotes

  1. NEMA, "DICOM Standard 2024 (PS3.1 - PS3.20)", National Electrical Manufacturers Association ────.
  2. IHE International, "IHE Radiology Technical Framework Volume 1-4", 2024 ────.
  3. HL7 International, "FHIR R4 ImagingStudy Resource", hl7.org/fhir/imagingstudy.html, 2024 ────.
  4. IEEE, "IEEE 11073 Personal Health Device Communication Standards", 2024 ────.
  5. RSNA, "RadLex Radiology Lexicon", Radiological Society of North America, radlex.org, 2024 ────.
  6. ISO 13485:2016, "Medical devices — Quality management systems", ISO ────.
  7. ISO 14971:2019, "Medical devices — Risk management", ISO ────.
  8. DICOM PS3.18, "Web Services (DICOMweb)", NEMA, 2024 ────.
  9. HL7 v2.x, "HL7 Version 2.5 Messaging Standard", HL7 International ────.
  10. SNOMED International, "SNOMED CT", snomed.org, 2024 ────.
  11. LOINC, "Logical Observation Identifiers Names and Codes", Regenstrief Institute, 2024 ────.
  12. ICD-10-CM, "International Classification of Diseases, 10th Revision", WHO, 2024 ────.
  13. NIST, "Health IT Standards and Test Tools", National Institute of Standards and Technology ────.
  14. ONC, "Office of the National Coordinator for Health IT Standards", HHS, 2024 ────.