Материал: part02

Скачать

Заказать новую работу

Внимание! Если размещение файла нарушает Ваши авторские права, то обязательно сообщите нам

Page 296​ DICOM PS3.2 2020a - Conformance​

Table H.4.2-21. Accepted Presentation Contexts By MAR-SCP AE​

 

 

Presentation Context Table​

 

 

Abstract Syntax​

 

Transfer Syntax​

Role​

Extended​

Name​

UID​

Name​

UID​

 

Negotiation​

 

 

Verification​

1.2.840.10008.1.1​ DICOM Implicit VR Little Endian​1.2.840.10008.1.2​

SCP​

None​

Substance​

1.2.840.10008.1.42​DICOM Implicit VR Little Endian​1.2.840.10008.1.2​

SCP​

None​

Administration​

 

DICOM Explicit VR Little Endian​1.2.840.10008.1.2.1​

 

 

Logging​

 

 

 

 

 

 

 

 

H.4.2.2.4.1.3 SOP Specific Conformance for Verification SOP Class​

The MAR-SCP AE provides standard conformance to the Verification SOP Class as an SCP.​

H.4.2.2.4.1.4 SOP Specific Conformance for Substance Administration Logging SOP Classes​

As required by the SOP Class, one of Patient ID or Admission ID must be present in the Substance Administration Logging request.​ If the request does not include the Patient ID, the MAR-SCP AE requests the Patient ID corresponding to the Admission ID from the​ Patient Registration System.​

TheMAR-SCPAESCPtranslatestheattributesshowninTableH.4.2-22intodatabasefieldsoftheMedicationAdministrationRecord​ System. All other provided attributes are converted to text strings and placed in the ClinicalNotes field of the database.​

Table H.4.2-22. Attributes of Logging Request Imported to Mar Database​

Patient ID​

(0010,0020)​

Product Package Identifier​

(0044,0001)​

Product Name​

(0044,0008)​

Substance Administration DateTime​

(0044,0010)​

Administration Route Code Sequence​

(0054,0302)​

Operator Identification Sequence​

(0008,1072)​

The MAR-SCP AE supports the N-ACTION Response Status return values and behavior shown in Table H.4.2-23.​

Table H.4.2-23. MAR-SCP AE N-ACTION Response Status Return Reasons​

Service​

Further Meaning​

Status Code​

Reason​

Status​

 

 

 

Success​

Success​

0000​

The log entry was successfully received and stored in the​

 

 

 

Medication Administration Record System database.​

Failure​

Processing failure​

0110​

The AE is unable to establish a session with the Medication​

 

 

 

Administration Record System (Error ID=C003), or with the​

 

 

 

Patient Registration System (Error ID=C002).​

 

 

 

Error message is output to the Service Audit Trail.​

 

Operator not authorized to add entry​C10E​

The AE received a user authorization rejection from the​

 

to Medication Administration Record​

Medication Administration Record System.​

 

 

 

Error message is output to the Service Audit Trail.​

 

Patient cannot be identified from​

C110​

The AE is unable to identify the Patient.​

 

Patient ID or Admission ID​

 

Error message is output to the Service Audit Trail.​

 

 

 

- Standard -​

 

 

DICOM PS3.2 2020a - Conformance​

Page 297​

Service​

Further Meaning​

Status Code​

 

Reason​

Status​

 

 

 

 

 

Update of Medication Administration​C111​

The Medication Administration Record System reported a​

 

Record failed​

 

database error.​

 

Error message is output to the Service Audit Trail.​

H.4.3 Network Interfaces​

H.4.3.1 Physical Network Interface​

TheEXAMPLE-MEDICATION-SYSTEM-GATEWAYsupportsasinglenetworkinterface.Oneofthefollowingphysicalnetworkinterfaces​ will be available depending on installed hardware options:​

Table H.4.3-1. Supported Physical Network Interfaces​

Ethernet 100baseT​

Gigabit Ethernet​

H.4.3.2 Additional Protocols​

EXAMPLE-MEDICATION-SYSTEM-GATEWAY conforms to the System Management Profiles listed in Table F.4.3-2. All requested​ transactions for the listed profiles and actors are supported. It does not support any optional transactions.​

Table H.4.3-2. Supported System Management Profiles​

Profile Name​

Actor​

Protocols Used​

Optional Transactions​Security Support​

Network Address Management​

DHCP Client​

DHCP​

N/A​

DNS Client​

DNS​

N/A​

 

H.4.3.2.1 DHCP​

DHCP can be used to obtain TCP/IP network configuration information. The network parameters obtainable via DHCP are shown in​ Table F.4.3-3. The Default Value column of the table shows the default used if the DHCP server does not provide a value. Values for​ network parameters set in the Service/Installation tool take precedence over values obtained from the DHCP server. Support for​ DHCP can be configured via the Service/Installation Tool. The Service/Installation tool can be used to configure the machine name.​ If DHCP is not in use, TCP/IP network configuration information can be manually configured via the Service/Installation Tool.​

 

Table H.4.3-3. Supported DHCP Parameters​

DHCP Parameter​

Default Value​

IP Address​

None​

Hostname​

Requested machine name​

List of NTP servers​

Empty list​

List of DNS servers​

Empty list​

Routers​

Empty list​

Static routes​

None​

Domain name​

None​

Subnet mask​

Derived from IP Address (see service manual)​

Broadcast address​

Derived from IP Address (see service manual)​

Default router​

None​

Time offset​

Site configurable (from Time zone)​

- Standard -​

Page 298​

DICOM PS3.2 2020a - Conformance​

DHCP Parameter​

Default Value​

MTU​

Network Hardware Dependent​

Auto-IP permission​

No permission​

If the DHCP server refuses to renew a lease on the assigned IP address all active DICOM Associations will be aborted.​

H.4.3.2.2 DNS​

DNS can be used for address resolution. If DHCP is not in use or the DHCP server does not return any DNS server addresses, the​ identity of a DNS server can be configured via the Service/Installation Tool. If a DNS server is not in use, local mapping between​ hostname and IP address can be manually configured via the Service/Installation Tool.​

H.4.4 Configuration​

H.4.4.1 AE Title/Presentation Address Mapping​

H.4.4.1.1 Local AE Titles​

The mapping from AE Title to TCP/IP addresses and ports is configurable and set at the time of installation by Installation Personnel.​

Table H.4.4-1. Default Application Entity Characteristics​

Application Entity​

Role​

Default AE Title​

Default TCP/IP Port​

PHARMACY-SCP​

SCP​

EX_PHAR_SCP​

5000​

MAR-SCP​

SCP​

EX_MAR_SCP​

4000​

The PHARMACY-SCP and MAR-SCP Application Entities can be configured to have the same AE Title.​

H.4.4.1.2 Remote AE Title/Presentation Address Mapping​

The mapping of external AE Titles to TCP/IP addresses and ports is configurable and set at the time of installation by Installation​ Personnel. This mapping is necessary for resolving the IP address and port of C-MOVE Destination Application Entities and must be​ correctly configured for the PHARMACY-SCP AE to correctly function as a C-MOVE SCP.​

H.4.4.2 Parameters​

Table H.4.4-2. Configuration Parameters​

Parameter​

Configurable​

Default Value​

General Parameters​

 

 

Maximum PDU size I can receive​

Yes​

128kbytes​

Maximum PDU size I can send​

Yes​

128kbytes​

Time-outwaitingforresponsetoTCP/IPconnect()request.(Low-leveltimeout)​

Yes​

10 s​

Time-out waiting for A-ASSOCIATE RQ PDU on open TCP/IP connection.​

Yes​

30 s​

(ARTIM timeout)​

 

 

Time-outwaitingforacceptanceorrejectionresponsetoanAssociationOpen​

Yes​

30s​

Request. (Application Level timeout)​

 

 

Time-out waiting for acceptance of a TCP/IP message over the network.​

Yes​

30 s​

(Low-level timeout)​

 

 

Time-out for waiting for data between TCP/IP packets. (Low-level timeout)​

Yes​

30 s​

PHARMACY-SCP AE Parameters​

 

Maximum number of simultaneous Associations​

Yes​

10​

- Standard -​

DICOM PS3.2 2020a - Conformance​

Page 299​

Parameter​

Configurable​

Default Value​

AEtime-outwaitingonanopenAssociationforthenextmessage(C-FIND-RQ,​

Yes​

1 minute​

Association Close Request. etc.) (DIMSE timeout)​

 

 

MAR-SCP AE Parameters​

 

 

Maximum number of simultaneous Associations​

Yes​

10​

AE time-out waiting on an open Association for the next Request message​

Yes​

1 minute​

(N-ACTION-RQ, Association Close Request. etc.) (DIMSE timeout)​

 

 

H.5 Media Interchange​

EXAMPLE-MEDICATION-SYSTEM-GATEWAY does not support Media Storage.​

H.6 Support of Extended Character Sets​

All EXAMPLE-MEDICATION-SYSTEM-GATEWAY DICOM applications support the following:​

ISO_IR 192 (Unicode)​

H.7 Security​

H.7.1 Security Profiles​

The EXAMPLE-MEDICATION-SYSTEM-GATEWAY is configurable to support the Kerberos Identity Negotiation Association Profile.​

H.7.2 Association Level Security​

The PHARMACY-SCP AE and the MAR-SCP AE can both be configured to accept Association Requests from only a limited list of​ Calling AE Titles. The SCP AEs can have different lists. Each SCP AE can be configured to check that the Association requestor​ specifies the correct Called AE Title for the SCP.​

In addition the IP address of the requestor can be checked. The SCP AEs can be constrained to only accept Association Requests​ from a configured list of IP addresses. The SCP AEs can have different lists.​

- Standard -​

Page 300​

DICOM PS3.2 2020a - Conformance​

- Standard -​

Смотрите также:

«ДОХОДЫ, РАСХОДЫ И ПРИБЫЛЬ КОММЕРЧЕСКОГО БАНКА.»
«ДОХОДЫ, РАСХОДЫ И ПРИБЫЛЬ КОММЕРЧЕСКОГО БАНКА.»
Значение, сущность и содержание социально — педагогической деятельности в организации для детей-сирот и детей, оставшихся без попечения родителей
__RGR2
__RGR2
_11_А. Франс для эл версии
_индив анализ данных
- Интерфейс 485 и оптопорт 11
:Конвергентный подход к проектированию дополнительных общеобразовательных общеразвивающих программ