0

我正在尝试将 dicom 文件(dicomized pdf 报告文件)发送到多个 PACS 系统。在某些情况下,我可以做到这一点,而在其他一些情况下,没有在我的日志中没有任何错误的情况下发送 dicom。

这是我的java代码:

public void sendDicomPdfToPacs(String dcmFilePath) throws Exception, IOException {

    Path tmpPdfDcm = Paths.get(dcmFilePath+".dcm");

    GlobalConfig cfg = new GlobalConfig();
    String localPacsAet = "";
    String localPacsIp="";
    int localPacsPort=0;
    localPacsAet = cfg.getLocalPacsAet1();
    localPacsPort = cfg.getLocalPacsPort1();
    localPacsIp = cfg.getLocalPacsIp();

    DcmEcho dcmEcho = new DcmEcho("device");
    dcmEcho.setRemoteHost(localPacsIp);
    dcmEcho.setRemotePort(localPacsPort);
    dcmEcho.setCalledAET(localPacsAet, true);
    dcmEcho.setCalling("DCMROUTER");

    Boolean dcmPacsStatus=false;

    try {
        dcmEcho.open();
        dcmPacsStatus=true;
        log.info("PACS is up and running");
        dcmEcho.close();
    } catch (IOException ex) {
        ...
    }


    if(dcmPacsStatus) {
        DcmSnd dcmsnd = new DcmSnd("device");

        //Set parameters AET
        dcmsnd.setCalledAET(localPacsAet);
        dcmsnd.setRemoteHost(localPacsIp);
        dcmsnd.setRemotePort(localPacsPort);
        dcmsnd.setCalling("DCMROUTER");

        //Set other default parameters
        dcmsnd.setOfferDefaultTransferSyntaxInSeparatePresentationContext(false);
        dcmsnd.setSendFileRef(false);
        dcmsnd.setStorageCommitment(false);
        dcmsnd.setPackPDV(true);
        dcmsnd.setTcpNoDelay(true);
        //Add DICOM file
        dcmsnd.addFile(tmpPdfDcm.toFile());
        // Configure transfer capability
        dcmsnd.configureTransferCapability();
        try {
            dcmsnd.start();
            log.info("Dicom Send initiated...");
        } catch (Exception e) {
            ...
        }

        try {
            long t1 = System.currentTimeMillis();
            dcmsnd.open();
            long t2 = System.currentTimeMillis();
            Logger.getLogger("Connected to " + localPacsAet + " in " + ((t2-t1)/1000F)+ "s");
            dcmsnd.send();
            dcmsnd.close();
            log.info("Released connection to " + localPacsAet);
        } catch (IOException e) {
           ...
        }  finally {
            dcmsnd.stop();

            /* delete dicom file! */
           ...

        }
    } else {
        log.info("Local PACS is down... Can not perform DICOM send request.");
    }
}

如果我尝试发送到 Osirix PACS,则 dicom 文件正在成功发送...

如果我尝试发送到其他 PACS 系统(例如 Agfa),那么我的日志中会收到以下消息:

Encapsulated Document:  (0042,0011) OB #795856 [25\50\44\46\2D\31\2E\33\0A\25\E2\E3\CF\D3\0A\31\20\30\20\6F\62\...]
MIME Type of Encapsulated Document:     (0042,0012) LO #16 [application/pdf]
2015-04-24 15:57:02 INFO  ProcessPdfReportFiles:487 - Going to perfom DICOM send request for file: C:\XXXXXXXX\5912.pdf.dcm to local pacs: PACS@10.37.5.50:104
38920 [DefaultQuartzScheduler_Worker-2] INFO org.dcm4che2.net.Association - Association(1) initiated Socket[addr=/10.37.5.50,port=104,localport=53580]
38920 [DefaultQuartzScheduler_Worker-2] INFO org.dcm4che2.net.PDUEncoder - PACS(1): A-ASSOCIATE-RQ PACS << DCMROUTER
39040 [device-2] INFO org.dcm4che2.net.Association - PACS(1): A-ASSOCIATE-AC DCMROUTER >> PACS
2015-04-24 15:57:02 INFO  ProcessPdfReportFiles:500 - PACS is up and running
39041 [DefaultQuartzScheduler_Worker-2] INFO org.dcm4che2.net.PDUEncoder - PACS(1) << A-RELEASE-RQ
39045 [device-2] INFO org.dcm4che2.net.Association - PACS(1) >> A-RELEASE-RP
39045 [device-2] INFO org.dcm4che2.net.Association - PACS(1): close Socket[addr=/10.37.5.50,port=104,localport=53580]
.2015-04-24 15:57:02 INFO  ProcessPdfReportFiles:535 - Dicom Send initiated...
39058 [DefaultQuartzScheduler_Worker-2] INFO org.dcm4che2.net.Association - Association(2) initiated Socket[addr=/10.37.5.50,port=104,localport=53581]
39059 [DefaultQuartzScheduler_Worker-2] INFO org.dcm4che2.net.PDUEncoder - PACS(2): A-ASSOCIATE-RQ PACS << DCMROUTER
39191 [device-3] INFO org.dcm4che2.net.Association - PACS(2) >> org.dcm4che2.net.pdu.AAssociateRJ: A-ASSOCIATE-RJ[result=1, source=1, reason=2]: 
permanent application-context-name-not-supported
39192 [device-3] INFO org.dcm4che2.net.Association - PACS(2): close Socket[addr=/10.37.5.50,port=104,localport=53581]

所以我猜这个特定的 PACS 拒绝了我的发送请求,因为:

A-ASSOCIATE-RJ[result=1, source=1, reason=2]: permanent application-context-name-not-supported

那么这是什么意思呢?我在这里想念什么?

4

2 回答 2

1

你是对的。PACS 可能不支持 Encapsulated PDF SOP 类。您可以通过将日志放在 DEBUG 上来获取更多信息 - 如果启用了 DEBUG 日志记录,您收到的 A-ASSOCIATE-RJ 消息将指示不支持哪些表示上下文(SOP 类 + 传输语法)。

http://medical.nema.org/dicom/2013/output/chtml/part08/sect_9.3.html是标准中的相关部分。

在 Agfa PACS 系统中简单地存储数据可能是可配置的。联系站点的 PACS 管理员并提供您建议的演示上下文,他们可能会添加它。

于 2015-04-24T14:38:51.110 回答
0

服务器提供的关联拒绝原因是“不支持应用程序上下文名称”。这意味着 SCU 正在为 SCP 不支持的应用程序上下文名称提议一个 UID。尝试使用 DICOM 3.0 的默认应用程序上下文名称 UID -“1.2.840.10008.3.1.1.1”

于 2015-04-24T21:53:09.030 回答