Nova postagem

Rechercher

Artigo
· Mar. 23 1min de leitura

クライアントーサーバ間の通信を暗号化する

これは、InterSystems FAQサイトの記事です。
 

クライアントーサーバ接続を担当するスーパーサーバで、SSLバージョン3とTLSバージョン1での通信が可能です。
このオプションを利用することで、通信上のデータを暗号化できます。

その他、Kerberosを使うことで通信上の暗号化も可能です。

Discussão (0)1
Entre ou crie uma conta para continuar
Discussão (7)4
Entre ou crie uma conta para continuar
Anúncio
· Mar. 22

[Video] FHIR Lessons Learned From the Field

Hi Community,

Enjoy the new video on InterSystems Developers YouTube:

⏯  FHIR Lessons Learned From the Field @ Global Summit 2024

 Watch for a range of use cases and insights from our global participation in FHIR projects, encompassing FHIR Repository, FHIR Façade, FHIR Transformations, and FHIR Client.  

Presenters: 
🗣 @Keren Skubach, Senior Sales Engineer, InterSyst
🗣 @Vic Sun, Sales Engineer, InterSystems
🗣 @Steve Mallam, HealthShare Team Lead, InterSystems  

Enjoy watching and look forward to more videos!👍

Discussão (0)1
Entre ou crie uma conta para continuar
Pergunta
· Mar. 22

HL7 OBX 5 modification resolved

I need to make changes to  OBX 5 which shows as immutable

I have tried ConstructClone, ThrowOnError, and Streams but I can't get the syntax correct

Example

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|142|REASON FOR REQUEST:      Total Cost:           0.00||||||O
                                        ^^^^ remove "REASON FOR REQUEST"                                                                            ^^ add cr/lf so down stream reports can be formatted more easily

 

I have the code done to parse out the "REASON FOR REQUEST" but I need to make the OBX 5 show the change.

Before:

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|142|REASON FOR REQUEST:      Total Cost:           0.00||||||O
OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|143|Special Instructions: ||||||O
OBX|2|CE|^PROVISIONAL DIAGNOSIS|1|R52^Pain, unspecified^I10|O|||||||||||test|\0x0A\0x0D\

After

OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|142|      Total Cost:           0.00||||||O

blank line added
OBX|1|TX|2000.02^REASON FOR REQUEST^AS4|143|Special Instructions: ||||||O
OBX|2|CE|^PROVISIONAL DIAGNOSIS|1|R52^Pain, unspecified^I10|O|||||||||||test|\0x0A\0x0D\

FYI

Set pRequest = ##class(EnsLib.HL7.Message).%OpenId(284)
Set pOutput = pRequest.%ConstructClone()
zw pOutput
pOutput=14@EnsLib.HL7.Message ; <OREF>

+----------------- general information ---------------
| oref value: 14
| class name: EnsLib.HL7.Message

| reference count: 2
+----------------- attribute values ------------------
| %ClonedId = 284
| %Concurrency = 1 <Set>
|%maps("runtimeIndex") = 149
|%maps("runtimeIndex",0) = ""
| AutoBuildMap = 0
| BuildMapStatus = ""
| CacheSegsGotten = 1
| DocType = "2.3:ORM_O01" <Set>
| DocTypeCategory = 2.3
| DocTypeName = "ORM_O01"
| Envelope = ""
| IsMutable = 1 <Set>     <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

I tried concantonating cr/lf.

The do statement doesn't work

 If (tItemNumberCount > 1) && (tTotalCostSegment > 0) {

                Set tOBXSegment = pRequest.GetSegmentAt("ORCgrp(1).OBRuniongrp.OBXgrp("_tTotalCostSegment_").OBX", .tStatus)

                Set tOBXText = tOBXSegment.GetValueAt(5)_"\X0D\\X0A\"  // Append escaped CR/LF representation

                Do tOBXSegment.SetValueAt(tOBXText, 5)     <<<<<<<<<<<<<<<<<<<<<<<<<<

            }

RESOLVED

I had to change the object for the send message

ElseIf (tMessageType="ORM") {
            //$$$ThrowOnError(..SendRequestAsync(..VistaTarget, pRequest, 1, "OutputCernerToVistaORM")) // can't use object, pRequest, created  for the HL7 message
            // 03272025 Must make a new command that uses the clone object instead of the HL7 message object which is immutable
            $$$ThrowOnError(..SendRequestAsync(..VistaTarget, pOutput, 1, "OutputCernerToVistaORM")) // Must use the object, pOutput,  created by the clone

27 Comments
Discussão (27)4
Entre ou crie uma conta para continuar
Anúncio
· Mar. 21

计划维护通知

🚨 计划维护通知 🚨

InterSystems 开发者社区将于明天(2025 年 3 月 22 日)美国东部时间上午 10:30 至下午 12:30(欧洲中部时间下午 16:30 至下午 18:30)进行计划维护。

在此期间,平台可能会出现间歇性停机。我们对给您带来的不便深表歉意,感谢您的耐心等待,我们将努力改进我们的服务。

感谢您的理解!

Maintenance Windows: Keep it short or use it all?

Discussão (0)1
Entre ou crie uma conta para continuar