RZDCX - Fast Strike DICOM Toolkit  Release 2.0.7.4
DICOM Structured Reporting

Structured Reporting Creation API. More...

Files

file  StructuredReport.dic
 This file is the structured reporting dictionary. This file hold SR Tree node definitions used by the methods in IDCXSR Structured Reporting Interface.

#
#  Copyright (C) 2009 - 2010, Roni Zaharia - RZ Software Services
# 
# /*! 
# This is the structured reporting dictionary.
# Each line represents an entry in the data dictionary.  
# Comments have a '#' at the beginning of the line.
# Every entry has the following columns, separated by tab.
#
# Mandatory Columns
# =================
# The first three (3) columns are mandatory and are the minimum for defining a node in the SR Tree.
#
# Column 1: Code
# --------------
# The code uniquely identifies a node in the structured report tree.
# This column is mandatory for every entry.
#
# Column 2: Designator
# --------------------
# The designator is the authority that is responsible for maintaining the code.
# This column is mandatory for every entry.
#
# Column 3: Meaning
# -----------------
# This is the human readable description of the code.
# This column is mandatory for every entry.
#
# Additional Columns
# ==================
# The additional columns are optional.
# Use the reserved word "NULL" to skip empty columns, For example, to set Units without specifiing version and UID.
#
# Column 4: Type
# --------------
# The type column AKA "Value Type" can be any of the valid SR document value types:
# -> TEXT
# -> CODE
# -> NUM
# -> DATETIME
# -> DATE
# -> TIME
# -> UIDREF
# -> PNAME
# -> SCOORD
# -> TCOORD
# -> COMPOSITE
# -> IMAGE
# -> WAVEFORM
# -> CONTAINER
#
# Value Type specific behavior when adding nodes
# ----------------------------------------------
# When adding a "CONTAINER", the next node will be added as a child for that container.
# To close the container, call UpOneLevel.
#
# When adding a "NUM", units are automatically added if specified.
# 
# Column 5: Version
# -----------------
# The version is an optional attribute further specializing the code.
# The ocde is unique within the dictionary and the version does not exend the key, only further describes it.
#
# Column 6: UID
# -------------
# Unique Identifier of the code, further identifing the code.
#
# Column 7: Units
# ---------------
# When the value type (Column 4) is NUM (Numeric) and Units are specified, the Units are automatically added when adding the code using AddDictValue.
# Referencial integrity of the units column is enforeced at runtime when attempting to add the code but not when loading the dictionary.
# If units are not specified for entry of type NUM, then the units must be explicitly set in runtime by using AddDictNumericValue. 
# In this case one should not use AddDictValue for this entry.
# 
# Column 8: Relationship
# ----------------------
# The relationship may be one of the valid values for SR Relation Types, enclosed by double quotes ("):
# The SR Relation Types currently defined in the standard are:
# -> "CONTAINS"
# -> "HAS OBS CONTEXT" meaning Has Observation Context
# -> "HAS ACQ CONTEXT" meaning Has Aquisition Context
# -> "HAS CONCEPT MOD" meaning Has Concept Modifier
# -> "HAS PROPERTIES"
# -> "INFERRED FROM" 
# -> "SELECTED FROM"
# 
# There is not validation on the actual string that is inserted.
# Relationship in the dictionary refers to the parent node.
# This means that if an entry has for example a relationship type of "Has Concept Modifier"
# then the entry further describes its parent node.
# If a relationship type is defined, then it is automatically added to the document tree.
#
# Code	Designator	Meaning	Type	Version	UID	Units	Relationship*
# ====	==========	=======	=========	=======	===	=====	============= 

209239	99PMP	"Epicenter"	SCOORD	NULL	NULL	NULL	"CONTAINS"
209074	99PMP	"Diagnostic Imaging Report"	CONTAINER	NULL	NULL	NULL	NULL
121070	DCM	"Findings"	CONTAINER	NULL	NULL	NULL	"CONTAINS"
G-C0E3	SRT	"Finding Site"	CODE	NULL	NULL	NULL	"HAS CONCEPT MOD"
T-35300	SRT	"Mitral Valve"
G-0380	SRT	"Right Ventricular Peak Systolic Pressure"	NUM	NULL	NULL	mm[Hg]	"CONTAINS"	
mm	UCUM	"millimeter"	UNITS	1.4
cm2	UCUM	"centimeter squared"	UNITS	1.4
mm[Hg]  UCUM	"millimeter of mercury"	UNITS
109041	DCM	"P Wave"	TCOORD	NULL	NULL	NULL	"CONTAINS"
SSDT	97PMP	"Study Start DateTime"	DATETIME	NULL	NULL	NULL "CONTAINS"
SEC		98PMP	"Study Start Time"	TIME	NULL	NULL	NULL	"CONTAINS"
121080	DCM	"Best illustration of finding"	IMAGE	NULL	NULL	NULL	"CONTAINS"

#
# EOF
#

.

 

Classes

interface  IDCXSR
 The DCXSR Interface is used for quickly creating DICOM Structured Reports. More...
 

Enumerations

enum  SR_CONTINUITY { SR_SEPARATE = 1, SR_CONTINUOUS = 2 }
 
enum  SR_GRAPHIC_TYPE {
  SR_GT_POINT = 1, SR_GT_MULTIPOINT = 2, SR_GT_POLYLINE = 3, SR_GT_CIRCLE = 4,
  SR_GT_ELLIPSE = 5
}
 SR Graphic Types to use for SCOORD nodes. More...
 
enum  SR_TEMPORAL_RANGE_TYPE {
  SR_TR_POINT = 1, SR_TR_MULTIPOINT = 2, SR_TR_SEGMENT = 3, SR_TR_MULTISEGMENT = 4,
  SR_TR_BEGIN = 5, SR_TR_END = 6
}
 SR Temporal Range Types to use for TCOORD nodes A TCOORD content item always have one or more children. More...
 
enum  SR_RELATIONSHIP_TYPE
 SR Relationship Types.
 

Detailed Description

Structured Reporting Creation API.

Enumeration Type Documentation

◆ SR_CONTINUITY

Container Node Continuity Type

Enumerator
SR_SEPARATE 

Separate Conetent Item.

SR_CONTINUOUS 

Continuous Conetent Item.

◆ SR_GRAPHIC_TYPE

SR Graphic Types to use for SCOORD nodes.

An SCOORD content item always have one or more IMAGE children Children are included by adding a Content Sequence. When an SCOORD value type content item is used it may have a concept name, which specifies the purpose of the reference to the spatial coordinates.

Enumerator
SR_GT_POINT 

POINT - a single point (x,y)

SR_GT_MULTIPOINT 

MULTIPOINT - multiple, independent points - pairs of (x,y)

SR_GT_POLYLINE 

POLYLINE - a closed polygon defined by its vertices - pairs of (x,y)

SR_GT_CIRCLE 

CIRCLE - a circle defined by its center and a point on the perimeter - two pairs of (x,y)

SR_GT_ELLIPSE 

ELLIPSE - an ellipse defined by the endpoints of its major and minor axes - four pairs of (x,y)

◆ SR_TEMPORAL_RANGE_TYPE

SR Temporal Range Types to use for TCOORD nodes A TCOORD content item always have one or more children.

Enumerator
SR_TR_POINT 

POINT - Temporal Range Type.

SR_TR_MULTIPOINT 

MULTIPOINT - Temporal Range Type.

SR_TR_SEGMENT 

SEGMENT - Temporal Range Type.

SR_TR_MULTISEGMENT 

MULTISEGMENT - Temporal Range Type.

SR_TR_BEGIN 

BEGIN - Temporal Range Type.

SR_TR_END 

END - Temporal Range Type.