Below is a concise reference table of the minimal DICOM attributes required to form a valid Modality Worklist (MWL) item in AlemHealth. The “Can Be Blank?” column reflects whether the element can be present but zero-length (Type 2) or must be non-empty (Type 1 or Type 1C) if included.
Reference: https://dicom.innolitics.com/ciods
| Name | Tag | Type | Can Be Blank? | Notes |
|---|---|---|---|---|
| Patient’s Name | (0010,0010) | 2 | Yes | Must exist in the dataset, but may be empty if truly unknown. |
| Patient ID | (0010,0020) | 2 | Yes | Same as above; tag must be present, can be blank. |
| Patient’s Birth Date | (0010,0030) | 2 | Yes | |
| Patient’s Sex | (0010,0040) | 2 | Yes | |
| Accession Number | (0008,0050) | 2 | Yes | Part of General Study Module; often used for scheduling but can technically be empty if unknown. |
| Study Date | (0008,0020) | 2 | Yes | |
| Study Time | (0008,0030) | 2 | Yes | |
| Referring Physician’s Name | (0008,0090) | 2 | Yes | |
| Study ID | (0020,0010) | 2 | Yes | |
| Requested Procedure ID | (0040,1001) | 1C | No (if included) | Type 1C: required if a Requested Procedure is actually scheduled. Typically non-empty in MWL use. |
| Requested Procedure Description | (0032,1060) | 1C | No (if included) | Either a description or a code (next row) must be present (Type 1C). |
| Requested Procedure Code Sequence | (0032,1064) | 1C | No (if included) | |
| Scheduled Procedure Step Sequence | (0040,0100) | 1 | N/A (must exist) | Must have at least 1 item containing the attributes below (all Type 1). |
| — Scheduled Station AE Title | (0040,0001) | 1 | No | |
| — Scheduled Procedure Step Start Date | (0040,0002) | 1 | No | |
| — Scheduled Procedure Step Start Time | (0040,0003) | 1 | No | |
| — Scheduled Procedure Step ID | (0040,0009) | 1 | No | |
| — Scheduled Procedure Step Status | (0040,0020) | 1 | No | Typically “SCHEDULED” or similar. |
| — Modality | (0008,0060) | 1 | No | e.g., “CT”, “MR”, “CR”, “US”, etc. |
Below is a concise mapping of the minimal DICOM MWL attributes to corresponding HL7 scheduling data fields. It illustrates how both systems align and helps ensure consistency when exchanging patient and procedure details.
TBA