Table 1.
XML format interface model.
| Tag name | Demonstration | Data flows | Data type | Event type |
|---|---|---|---|---|
| Grids | For a split screen, output m × n section pictures at a time. Format: m/n | Client initiated | Integer | Interactive request |
| SliceSq | For a slice sequence, multiple sets of MPR/MIPs child nodes could be embedded | Client initiated | With child nodes | |
| MPR | Used to represent the positions of the coronal plane, cross section, and sagittal plane, respectively. Format: X/Y/Z, for example, 20/NULL/NULL represents getting a coronal plane whose coordinate is (20,0,0). | Client initiated | Integer | |
| MIPs | Includes four types: MIP, MinIP, AVG, and NULL. If the MIPs are not NULL, format: MIPs type [interval] | Client initiated | Text | |
| Time | Occurrence time of client interaction | Client initiated | DateTime | Interactive object |
| PACS_id | Unique identification number of a group of SMIs from PACS | Client initiated | Text | |
| User | Account and IP address of client | Client initiated | Text | |
| State | Response status of the AIIA, including Request, Loading, Processing, and Done | AIIA response | Text | Blocking feedback |
| Proj | Projection (2D pictures) from the AIIA rendering, recorded with hex stream text after zip packing | AIIA response | Text | |
| PipeNo | For a data flow pipeline, a group of SMIs could be independently operated by multiple clients with different pipelines. | Client initiated | Text | Pipeline management |
| Init | Recorded as true or false depending on whether it is the first requested operation of the dataset by the client. | Client initiated | Boolean |