OpenIGTLink US messaging proposal

This page is part of http://wiki.na-mic.org/Wiki/index.php/2016_Winter_Project_Week:TrackedUltrasoundStandardization.

Status message format

The status can be organized as a xml document, and can thus be embedded into any text field in any message. XML also provides an easy system for optional and extension parameters. Each DOM-element can contain a reserved extension element. Here custom properties can be added without interfering with the required/optional properties.

Complete description of all properties for an ultrasound server:

The following are properties for a server residing on an ultrasound scanner. The structure is given in pseudocode, but the intended format is XML.

Parameters are either required, optional or extension.

• required: Defined by standard. Must be present in order to comply with standard.
• optional: Defined by standard. Might be present, if available from scanner and implemented.
• extension: not part of the standard, but added by vendor.
• Available_applications { list of names } (list of applications/presets available on the scanner)
• Application_name { string }
• Available_Probes { device_id list } ( List of all probes currently attached to the scanner.)
• Available_Streams : (these are an exhaustive list of all stream types that can be of interest from a scanner. Only those supported by the scanner are given. The scalar variants contain raw data, while the RGB/Gray versions are suitable for direct screen display. LUTs can be available when using the raw variants.)
  • Display, (RGB)
  • US_B-Mode (Gray)
  • US_B-Mode-Raw (Scalar)
  • US_Color-Doppler (RGB)
  • US_Color-Doppler-Velocity (Scalar)
  • US_Power-Doppler (RGB)
  • US_Elastography (RGB)
  • US_Elastography (Scalar)
  • US_R0 (Scalar)
  • US_R1 (Scalar)
  • US_RF (Scalar)
  • US_IQ (Complex)
• Probe: device_id,
  • probe parameters: Name, Center freq, focus pt, pitch, geometry model..?,