#HealthShare

What I can do:
Get a subset of HL7 messages.
Send the messages to a RecordMap (with key fields from the HL7 message).
Save each message to a file.

How can I send all messages until a set time (e.g. 9am each day) to single file?

Scenario:
In the period 09:00 1 Jan 2022 to 09:00 2 Jan 2022 there are say 50 messages to save to file: File001.txt
In the period 09:00 2 Jan 2022 to 09:00 3 Jan 2022 there are say 40 messages to save to file: File002.txt
etc

Hello,

We are very interested about studying DICOM in deep, both the standar itself and how it is related to HealthShare.

Could you please point us to some good references: documentation, courses, books, pdfs, explanations; to understand what is this standard about and how works.

Thanks for your replies

We have read:

https://dicom.nema.org/medical/dicom/current/output/html/part01.html

I've disabled TLS v1.0 and 1.1 within Healthshare setting, but still seeing these error messages when running a security scan. We do have apache being used. What else can I try?

Error messages:

Hi Community,

I have created Tier 1 CCR and when I move it to Live it shows the below error.

I initially had changes deployed through a different CCR to the TEST environment and were not deployed to LIVE for the same class.

I tried to cancel it so that I can move these latest changes but I still get the below message.

Hi Community,

I am getting the below error when searching for a patient who has medications on the clinical viewer.

What could be the issue?

Hi All,

Is there any cache command which can give who all has compiled a classes from the day it has been created. Specifically I want the 2 information username and time of compilation of class.

I tried with $$DATE^%R("TEST.1.INT"), but it only gives the last compilation time.

Thanks in advance !!

A mistake happened and records were assigned the wrong assigning authority name: PID3.4.

Everything else was correct. This resulted in duplicate records. Ex

Record 1: MRN1 has AA1 and clinical data

Record 2: MRN1 has AA2 and the same clinical data as Record 1 + more clinical data that is not in Record 1

I would like to remove Record 2 ensuring that there are no orphan records left.

Does anyone have insight into how the Stream Global Compression works in 2022? I'm particularly interested in the XDSb repository on the Edges. As I understand it anything new will be compressed. Is there a compression method that is used that can be utilized by other code? How are the retrievals aware that the contents are compressed in order to de-compress them?