hello @Ravikumar Puvvala, I do not believe that IRIS currently supports the following features that you require as per my knowledge and research. 

Here i will upload a link to the official documentation of the HL7 / FHIR ( changes made and how to handle them ) post. 

i hope this will be useful for you. 

http://hl7.org/fhir/comparison-v2.html

Regards. 

hello there @Neerav Verma 
​​​​​​ Here are a few links for you to refer on how you could encode and upload a raw text to Azure Blob. 

https://docs.microsoft.com/en-us/dotnet/api/microsoft.azure.storage.blob...

https://stackoverflow.com/questions/12788350/how-to-upload-a-text-string...

Here is also a video link :

http://youtube.com/watch?v=Z9HeNZ8lmi4

I hope that you find it helpful and solves your problem. 

Regards. 

Hello there @Mohamed Haneeq . 
warmly welcoming you  to the community. 

Well answering to your question, I would suggest that going along with IRIS will be the best and perfect match for you as per your requirement. 

And also i will add the link to from which you can download CACHE as well as IRIS and try it out for free. 

https://hub.docker.com/_/intersystems-iris-for-health

 https://hub.docker.com/_/intersystems-iris-for-health
https://aws.amazon.com/marketplace/pp/B07N87JLMW?qid=1587469562959&sr=0-...
https://azuremarketplace.microsoft.com/en-us/marketplace/apps/intersyste...
https://console.cloud.google.com/marketplace/details/intersystems-launch...
 
 https://download.InterSystems.com

Hope I have answered your question and wish you a best of luck. 

Hello there Cedric,


I am a guy who is enthusiastic with Networking and the good news is that, Yes I have used the TCPKeepAlive function. 
For you to understand this function you should be aware of a protocol named NAT or also known as Natting and TCP or also known as the Transmission Control Protocol.


A keepalive signal is often sent at predefined intervals, and plays an important role on the Web/Internet. After a signal is sent, if no reply is received the link is assumed to be down and future data will be routed via another path until the link is up again. A keepalive signal can also be used to indicate to Internet infrastructure that the connection should be preserved. Without a keepalive signal, intermediate Natting or the NAT enabled router can drop the connection after time out. 


Since the only purpose is to find links that don't work or to indicate connections that should be preserved, keepalive messages tend to be short and not consume or take much of the Bandwidth. 

There are 3 types of TCP KeepAlive functions available. 


1.Keepalive time is the duration between two keepalive transmissions in idle condition. TCP keepalive period is required to be configurable and by default is set to no less than 2 hours.
2.Keepalive interval is the duration between two successive keepalive retransmissions, if acknowledgement to the previous keepalive transmission is not received.
3.Keepalive retry is the number of retransmissions to be carried out before declaring that remote end is not available

When two hosts are connected over a network via TCP/IP, TCP Keepalive Packets can be used to determine if the connection is still valid, and terminate it if needed.

Most hosts that support TCP also support TCP Keepalive. Each host (or peer) periodically sends a TCP packet to its peer which solicits a response. If a certain number of keepalives are sent and no response acknowledgement or also known as the (ACK) is received then the sending host will terminate the connection from its end. If a connection has been terminated due to a TCP Keepalive time-out and the other host eventually sends a packet for the old connection, the host that terminated the connection will send a packet with the Reset Flag or also known as the RST flag set to signal the other host that the old connection is no longer active. This will force the other host to terminate its end of the connection so a new connection can be established.

All this takes place in terms of a 3 Way hand shake procedure. 

Typically TCP Keepalives are sent every 45 or 60 seconds on an idle TCP connection, and the connection is dropped after 3 sequential ACKs are missed.

This is just only a fraction of what I can tech you. There is much more on this like the HTTP keep alive and so on. 

I hope that I have answered your question.  

If there is anything else that you would like to know please feel free to ask me. 

Regards.