... h2. Description
Private Study Management Service SCP
h2. Dependencies
!studyMgtScp.gif!
h2. Attributes
h4.CalledAETitles {anchor:CalledAETitles}
List of accepted called AE titles, separated by \ (backslash).
h4.CallingAETitles {anchor:CallingAETitles}
List of accepted calling AE titles, separated by \ (backslash).
ANY = accept any.
h4.IgnoreStudyDeleteFailed {anchor:IgnoreStudyDeleteFailed}
|
Ignore study deletion failures if the study was not found.
|
h4. [#PatientMatching] {anchor:PatientMatching}
Defines which Patient Attributes in received N-CREATE requests shall be considered for the selection of an existing
Patient record in the archive.
*Format*: 'pid' \['?'\] ',issuer' \['?'\] \[','<demograhic-match>\]
<demograhic-match> ::= '\[' <demograhic-fields> '\]' | <demograhic-fields>
<demograhic-fields> ::= <demograhic-field> \['?'] \[',' ...\]
<demograhic-field> ::= 'familyname' | 'givenname' | 'middlename' | 'birthdate'
A question mark('?') after a attribute name specifies that a missing value in received N-CREATE requests will match with any value for that attribute in existing Patient Records, as Patient Records with missing values for that attribute will match with any value for that attribute in received MPPS N-CREATE requests. Attribute names without question marks specifies, that MPPS N-CREATE requests without values for such attributes will not match any existing Patient Record, as Patient Records without values for such attributes will not get selected on receive of any N-CREATE request.
With 'pid*?*', you have to configure the Patient's family name complex ('familyname') as additional matching criterium.
Surrounding <demograhic-match> by brackets('[]') defines, that demographic fields shall *not* be considered for the selection of an existing Patient record, if the Patient ID is qualified by an Issuer/Authority in the received N-CREATE request *and* in the matching Patient Record.
*Default Value:* {{pid,issuer?\[familyname,givenname,middlename?,birthdate\]}}
|
h4.AcceptedTransferSyntax {anchor:AcceptedTransferSyntax}
|
... List of accepted Transfer Syntaxes. Order defines selection preference. Use either the Transfer Syntaxes UID value or following defined symbolic names:
- ImplicitVRLittleEndian,
- ExplicitVRLittleEndian,
- DeflatedExplicitVRLittleEndian,
- ExplicitVRBigEndian
h4.MaximumPDULength {anchor:MaximumPDULength}
Maximum protocol data unit (PDU) package length for receiving PDUs.
{warning}
This property should be set to equal values for all DICOM SCP services with same called AE Title(s). Otherwise it is non-deterministic, which configured value is effective.
{warning}
h4.MaximumOperationsInvoked {anchor:MaximumOperationsInvoked}
The maximum number of outstanding operations and/or sub-operations it allows the Association-requester to invoke asynchronously. A value of zero indicates an unlimited number of outstanding operations.
{warning}
This property should be set to equal values for all DICOM SCP services with same called AE Title(s). Otherwise it is non-deterministic, which configured value is effective.
{warning}
h4.MaximumOperationsPerformed {anchor:MaximumOperationsPerformed}
The maximum number of outstanding operations and/or sub-operations it allows the Association-requester to perform asynchronously. A value of zero indicates an unlimited number of outstanding operations.
{warning}
This property should be set to equal values for all DICOM SCP services with same called AE Title(s). Otherwise it is non-deterministic, which configured value is effective.
{warning}
h4.EjbProviderURL {anchor:EjbProviderURL}
Identifies JNDI (e.g: jnp://hostname:1099) with EJBs.
"LOCAL", if EJBs are deployed in same JBoss instance.
h4.DcmServerName {anchor:DcmServerName}
Used internally. Do not modify.
h4.AuditLoggerName {anchor:AuditLoggerName}
Used internally. Do not modify.
h4.Name {anchor:Name}
The class name of the MBean
h4.State {anchor:State}
The status of the MBean
h4.StateString {anchor:StateString}
The status of the MBean in text form
h2. Operations
h4.create {anchor:create}
Standard MBean lifecycle method
h4.start {anchor:start}
The start lifecycle operation
h4.stop {anchor:stop}
The stop lifecycle operation
h4.destroy {anchor:destroy}
The destroy lifecycle operation
h4.jbossInternalLifecycle {anchor:jbossInternalLifecycle}
The detyped lifecycle operation (for internal use only)
h2. Notifications
|
E-mail