Difference between revisions of "OpenIGTLink/ProtocolV2/Type/ImageMeta"
| Line 84: | Line 84: | ||
Ziv Yaniv:<br> | Ziv Yaniv:<br> | ||
| − | The fixed size of "Patient name" and "Patient id" can potentially lead to buffer overflow. If treating the king of Spain you will need all 64 characters "Juan Carlos Alfonso Víctor María de Borbón y Borbón-Dos Sicilias". Possibly separate each field into two, something like "Patient Name Length" (unsigned int - 16 bits) and then "Patient Name". | + | The fixed size of "Patient name" and "Patient id" can potentially lead to buffer overflow. If treating the king of Spain you will need all 64 characters "Juan Carlos Alfonso Víctor María de Borbón y Borbón-Dos Sicilias". Possibly separate each field into two, something like "Patient Name Length" (unsigned int - 16 bits) and then "Patient Name". I believe that all names are shorter than 65535 characters |
Revision as of 19:29, 1 July 2010
Home < OpenIGTLink < ProtocolV2 < Type < ImageMetaContents
Summary
The IMGMETA message is used to transfer image meta information which are not available in IMAGE message type, such as patient name, medical record number, modality etc. An IMGMETA message can contain meta data for multiple images. This message type may be used to obtain a list of images available in the remote system, such as image database or commercial image-guided surgery (IGS) system.
Message Types
IMGMETA
| Data | Type | Description |
| Name/Description | char[64] | Name or description of the image |
| Id | char[20] | Id to query the IMAGE and COLORT |
| Modality | char[32] | String which specifies the modality |
| Patient name | char[64] | Name of the patient |
| Patient id | char[64] | Id of the patient |
| Timestamp | 64 bit unsigned | Scan time, see OpenIGTLink/Timestamp |
| RI, RJ, RK | 16 bit unsigned | Number of pixels in each direction (same as in IMAGE) |
| S | 8 bit unsigned | Scalar type (e.g. 3:uint8, 5:uint16, same as in IMAGE) |
| -- | 8 bit unsigned | Reserved |
- More than one item can be transmitted. The number is bodySize/itemSize.
- To get the IMAGE, GET_IMAGE is used with the Id in the device name field.
GET_IMGMETA
| Data | Type | Description |
STT_IMGMETA
N/A
STP_IMGMETA
N/A
Implementations
IMGMETA message type is implemented in the following source code.
Contributors
Alexander Schaal
Comments
Ziv Yaniv:
The fixed size of "Patient name" and "Patient id" can potentially lead to buffer overflow. If treating the king of Spain you will need all 64 characters "Juan Carlos Alfonso Víctor María de Borbón y Borbón-Dos Sicilias". Possibly separate each field into two, something like "Patient Name Length" (unsigned int - 16 bits) and then "Patient Name". I believe that all names are shorter than 65535 characters
