Maybe web terminal?
- Log in to post comments
Maybe web terminal?
In IRIS you can define the name of the property when the object is transformed into a JSON:
https://docs.intersystems.com/irislatest/csp/documatic/%25CSP.Documatic…
In your case I suggest you to follow the idea of @Robert Cemper ...and update your Cache as soon as possible!
Google is our friend!
https://knowledge.informatica.com/s/article/507491?language=en_US
Just to confirm, can you check your licence and confirm that FHIR SQL Builder is included?
.png)
Good point @Patrick Jamieson !
But... Will be there enough time to evolve and to implement it before to the next wonder standard?
A model where the data storage is OpenEHR and the data transfer is FHIR is seen by some as the best of both worlds
Implement that would be the perfect punishment for all my sins! 😂
Thank you very much! Always is a pleasure to be helpful!
That's great! Many customers use Jasper reports and this example will be really helpful.
Just to go deeper in the Oliver's answer and because I'm always strugling against the certificates and I hate them...you can see here an example about the generation of a self-signed certified in wich you define the "Common name", the equivalent to your domain, in your case the Common name used to generate the certificate is Test111a.domain.local so you need a new one with the new domain as @Oliver Wilms told you.
Reading the doc (https://docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cl…) looks like your response has a problem with a list property but I can't say more with just a screenshot.
We have a lot of documentation about XML transformations, you can start with this
My suggestion, try to get the schema of the CCDA (a XSD file) and import it into IRIS (Interoperate -> XML -> XML SCHEMA STRUCTURES) in order to work better with a Virtual Document based on your CCDA files. Then you can use regular DTL to transform it into another objects or directly access to each field of the document with methods as GetValueAt (documentation)
About the Inbound Adapters here is the documentation related and for the Outbound Adapter...if you want to export it into a flat file or a CSV any FileOperation would be enough.
Well, for R5 version we have now 157 resources... The snowball is growing and growing.
Hi @Yone Moreno !
You can do something like this to filter messages with no OBX:
.png)
Do a foreach by OBX, in case that OBX exists you can redirect the message to the proper business component and jump out of the loop. @withOBX is a local variable to check if exists any OBX segment, if the value is "0" then there is no OBX segments and you can redirect the message to another business component.
Click on "when" not in "rule" before to click on "+".
Did you import tiktoken into your embedded python method?
Hi @Krista Koljonen take a look at this page of the documentation. There are many options available to check the status of active productions using the API Rest.
You can stop the mirror on the server that is running on backup but...why?
You are welcome @Lorenzo Scalese ! Always a pleasure to be helpful.
Well, I've seen a couple of public tenders requesting Dynatrace for monitoring. I'll take a look at it Does anyone experience on it?
Try this url for Docker containers:
https://containers.intersystems.com/contents
About the eval download, it's working for me.
Documentation is your friend!
To configure properly the IRIS metrics like queue alerts and so on you can check this configurations:
Could you be more specific about what point or step you don't understand?
Well, I think that you should try first a Learning Path, try this one:
We can see here the differences between R4 and R5 releases of FHIR. I can't imagine an organization migrating FHIR respositories every 3 or 4 years to keep updated to the latest version. What I forsee it's a future with a lot of organizations using different versions of FHIR and trying to communicate among them struggling against the differences...exactly the same that we have right now.
Just a small correction, 6 is the normative level.
Ineed, the normative resources won't be modified in the future but the devil is in the detail. More and more resources below the level 4 will be used by organizations that would find out major changes on it in future versions.