The semantic impacts of the above mentioned options is clear for the majority of options. Some particular
options, however, are so specific that they need detailed descriptions which will be given in this
passage.
The returned character set options are intended for situations in which the wlmscpfs application will
return attribute values which are not composed of characters from the DICOM default character repertoire.
In such cases, for example option --return-iso-ir-100 can be used to specify that a response to a
modality's worklist management C-FIND request shall contain DICOM's Specific Character Set attribute
(0008,0005) with a corresponding value, indicating the character repertoire from which the characters of
returned attribute values were taken (in this example the repertoire ISO IR 100). Please note that the
wlmscpfs application will not make sure that all returned values are actually made up of this character
repertoire; the application expects this to be the case.
In general, the Specific Character Set attribute (0008,0005) will only be included in the C-FIND response
if it contains any attributes that are affected by the character set, i.e. for value representations PN,
LO, LT, SH, ST and UT.
Please note that a C-FIND request which is handled by this application may contain DICOM's Specific
Character Set attribute (0008,0005), but this application will never use this attribute's value for
matching. Besides, the question if DICOM's Specific Character Set attribute (0008,0005) will be contained
in a C-FIND response which is returned by this application is always determined by the returned character
set option which was specified when this application was started.
The options --enable-file-reject and --disable-file-reject can be used to enable or disable a file
rejection mechanism which makes sure only complete worklist files will be used during the matching
process. A worklist file is considered to be complete if it contains all necessary type 1 information
which the SCP might have to return to an SCU in a C-FIND response message. Table K.6-1 in part 4 annex K
of the DICOM standard lists all corresponding type 1 attributes (see column 'Return Key Type').
WritingRequestFiles
Providing option --request-file-path enables writing of the incoming C-FIND requests into text files. The
option value provides the target directory where these files will be stored. All request files are stored
in 'dump' format as provided by the dcmdump tool and are raw, i.e. they are written as they arrive at
wlmscpfs, without any tag processing applied by wlmscpfs.
Writing request files allows users to 'interactively' prepare the worklist database (for wlmscpfs the
worklist files served from the --data-file-path directory) by watching the request file directory. Once a
request file appears, one needs some time to update worklist entries in the database. For that reason it
makes sense to use --request-file-path in combination with option --sleep-before which lets users specify
a certain amount of seconds that wlmscpfs should wait before actually starting to check the worklist
database. Note that the request files written with --data-file-path are not automatically deleted by
wlmscpfs.
If request files are enabled, wlmscpfs must automatically create file names within the given directory.
By default, the format is <timestamp>.dump where <timestamp> is in the format YYYYMMDDhhmmssffffff where:
• YYYY is the current year
• MM is the current month
• DD is the current day
• hh are the current hours (in 24 hour format)
• mm are the current minutes
• ss are the current seconds and
• ffffff is the fraction of the current second
This should work as a default for most applications that would like to use request files and want to
ensure unique file names. If it is desired to change this naming scheme, the option --request-file-format
can be used. It permits one to specify the file naming pattern used by --request-file-path.
For flexibility, the following placeholders can be used in the pattern provided for --request-file-format:
• #a: calling application entity title of the peer SCU
• #c: called application entity title (AE title of worklist SCP application)
• #i: process id of the worklist SCP application process handling the request
• #p: patient ID if present, otherwise empty string
• #t: timestamp in the format YYYYMMDDhhmmssffffff
The default (i.e. the value if --request-file-format is not explicitly set) is #t.dump resulting in the
timestamp format described above.
An example for such a user-defined format string would be 'request_#i_#a_#c.txt'. The #i makes most sense
if wlmscpfs multi-process mode is enabled via --fork option in order to ensure that simultaneous request
will not result in the same file name for both requests.
It should be noted that the #p placeholder uses the value of Patient ID (0010,0020) from the request as
is, i.e. if the string contains non-ASCII characters, the file name computed by wlmscpfs might be broken
and thus cannot be written successfully or will look broken once written. Also, an empty Patient ID is
used as such, i.e. the #p will be replaced with an empty string.
DICOMConformance
The wlmscpfs application supports the following SOP Classes as an SCP:
VerificationSOPClass 1.2.840.10008.1.1
FINDModalityWorklistInformationModel 1.2.840.10008.5.1.4.31
The wlmscpfs application will accept presentation contexts for all of the abovementioned supported SOP
Classes using any of the transfer syntaxes:
LittleEndianImplicitTransferSyntax 1.2.840.10008.1.2
LittleEndianExplicitTransferSyntax 1.2.840.10008.1.2.1
BigEndianExplicitTransferSyntax 1.2.840.10008.1.2.2
The default behavior of the wlmscpfs application is to prefer transfer syntaxes having an explicit
encoding over the default implicit transfer syntax. If wlmscpfs is running on big-endian hardware it will
prefer BigEndianExplicit to LittleEndianExplicit transfer syntax (and vice versa). This behavior can be
changed with the --prefer options (see above).
If compiled with zlib support enabled (see --version output) and if option --prefer-deflated is used,
also the following transfer syntax is accepted.
DeflatedExplicitVRLittleEndianTransferSyntax 1.2.840.10008.1.2.1.99
The wlmscpfs application does not support extended negotiation.
Currently, the wlmscpfs application supports the following attributes as matching keys:
(0008,0020) StudyDate
(0008,0030) StudyTime
(0008,0050) AccessionNumber
(0008,0090) ReferringPhysicianName
(0010,0010) PatientName
(0010,0020) PatientID
(0010,0021) IssuerOfPatientID
(0010,0030) PatientBirthDate
(0010,0040) PatientSex
(0010,2297) Responsible Person
(0010,2298) Responsible Person Role
(0032,1032) RequestingPhysician
(0038,0010) AdmissionID
(0040,0100) ScheduledProcedureStepSequence
(0008,0060) > Modality
(0040,0001) > ScheduledStationAETitle
(0040,0002) > ScheduledProcedureStepStartDate
(0040,0003) > ScheduledProcedureStepStartTime
(0040,0006) > ScheduledPerformingPhysicianName
(0040,1001) RequestedProcedureID
(0040,1003) RequestedProcedurePriority
As return keys the following attributes are currently supported by wlmscpfs:
(0008,0020) StudyDate
(0008,0030) StudyTime
(0008,0050) AccessionNumber
(0008,0080) InstitutionName
(0008,0081) InstitutionAddress
(0008,1040) InstitutionalDepartmentName
(0008,0090) ReferringPhysicianName
(0008,1080) AdmittingDiagnosesDescription
(0008,1110) ReferencedStudySequence
(0008,1150) > ReferencedSOPClassUID
(0008,1155) > ReferencedSOPInstanceUID
(0008,1120) ReferencedPatientSequence
(0008,1150) > ReferencedSOPClassUID
(0008,1155) > ReferencedSOPInstanceUID
(0010,0010) PatientName
(0010,0020) PatientID
(0010,0021) IssuerOfPatientID
(0010,0030) PatientBirthDate
(0010,0040) PatientSex
(0010,1000) OtherPatientIDs (retired)
(0010,1001) OtherPatientNames
(0010,1020) PatientSize
(0010,1030) PatientWeight
(0010,1040) PatientAddress
(0010,1080) MilitaryRank
(0010,2000) MedicalAlerts
(0010,2110) ContrastAllergies
(0010,2160) EthnicGroup
(0010,21a0) SmokingStatus
(0010,21b0) AdditionalPatientHistory
(0010,21c0) PregnancyStatus
(0010,21d0) LastMenstrualDate
(0010,2297) ResponsiblePerson
(0010,2298) ResponsiblePersonRole
(0010,4000) PatientComments
(0020,000d) StudyInstanceUID
(0032,1032) RequestingPhysician
(0032,1033) RequestingService
(0032,1060) RequestedProcedureDescription
(0032,1064) RequestedProcedureCodeSequence
(0008,0100) > CodeValue
(0008,0102) > CodingSchemeDesignator
(0008,0103) > CodingSchemeVersion
(0008,0104) > CodeMeaning
(0038,0010) AdmissionID
(0038,0011) IssuerOfAdmissionID
(0038,0050) SpecialNeeds
(0038,0300) CurrentPatientLocation
(0038,0500) PatientState
(0040,0100) ScheduledProcedureStepSequence
(0008,0060) > Modality
(0032,1070) > RequestedContrastAgent
(0040,0001) > ScheduledStationAETitle
(0040,0002) > ScheduledProcedureStepStartDate
(0040,0003) > ScheduledProcedureStepStartTime
(0040,0004) > ScheduledProcedureStepEndDate
(0040,0005) > ScheduledProcedureStepEndTime
(0040,0006) > ScheduledPerformingPhysicianName
(0040,0007) > ScheduledProcedureStepDescription
(0040,0008) > ScheduledProtocolCodeSequence
(0008,0100) > > CodeValue
(0008,0102) > > CodingSchemeDesignator
(0008,0103) > > CodingSchemeVersion
(0008,0104) > > CodeMeaning
(0040,0009) > ScheduledProcedureStepID
(0040,0010) > ScheduledStationName
(0040,0011) > ScheduledProcedureStepLocation
(0040,0012) > PreMedication
(0040,0020) > ScheduledProcedureStepStatus
(0040,0400) > CommentsOnTheScheduledProcedureStep
(0040,1001) RequestedProcedureID
(0040,1002) ReasonForTheRequestedProcedure
(0040,1003) RequestedProcedurePriority
(0040,1004) PatientTransportArrangements
(0040,1005) RequestedProcedureLocation
(0040,1008) ConfidentialityCode
(0040,1009) ReportingPriority
(0040,1010) NamesOfIntendedRecipientsOfResults
(0040,1400) RequestedProcedureComments
(0040,2001) ReasonForTheImagingServiceRequest
(0040,2004) IssueDateOfImagingServiceRequest
(0040,2005) IssueTimeOfImagingServiceRequest
(0040,2008) OrderEnteredBy
(0040,2009) OrderEnterersLocation
(0040,2010) OrderCallbackPhoneNumber
(0040,2016) PlacerOrderNumberImagingServiceRequest
(0040,2017) FillerOrderNumberImagingServiceRequest
(0040,2400) ImagingServiceRequestComments
(0040,3001) ConfidentialityConstraintOnPatientDataDescription
The attribute (0008,0005) SpecificCharacterSet is a special case and its support by wlmscpfs is discussed
in the NOTES section above.
AccessControl
When compiled on Unix platforms with TCP wrapper support, host-based access control can be enabled with
the --access-control command line option. In this case the access control rules defined in the system's
host access control tables for wlmscpfs are enforced. The default locations of the host access control
tables are /etc/hosts.allow and /etc/hosts.deny. Further details are described in hosts_access(5).