go to post Jenna Poindexter · Oct 22, 2019 Definately would always recommend full commands. I remember the day when we had to write code this way however it isn't the case anymore. That said, it's good to be able to read code like this because it still exists out there.
go to post Jenna Poindexter · Oct 22, 2019 This is referring to mapping between SDA and Health Insight cubes. Please PM me so we can discuss your need further. I am one of the Sales Engineers working with the VA.
go to post Jenna Poindexter · Oct 21, 2019 Simply select the code to convert and then select Edit -> Advanced - And then either Expand or Compress Commands.
go to post Jenna Poindexter · Oct 21, 2019 I think full commands are much easier to read for those that might be coming into your organization and will be taking over development of your projects in the future. It's pretty easy to convert from one to the other using the Expand and Compress commands option in Studio. For those that might be visually impaired, it would be a lot easier to dictate expanded commands than abbreviated versions. Just my 2 cents
go to post Jenna Poindexter · Oct 20, 2019 Hi Richard- I'm assuming you are working for or with VA as the build you mention is a specific build provided to the VA. I don't believe that the FHIR annotations were released until version 2018.x of HealthShare. If you can reach out to the VA sales engineers via email we'd be happy to get you a copy.
go to post Jenna Poindexter · Oct 20, 2019 If you are running IRIS for Health From the management portal, assuming you have a Foundation namespace created you can click Health -> <select foundation namespace> -> Schema Documentation -> FHIR Annotations If you do not have a foundation namespace created, click Health -> Install Wizard -> Configure Foundation Enter the name for the Namespace, click Save and then click Activate Once you have created a Foundation namespace you should be able to access the FHIR Annotations as mentioned above. The same holds true for Health Connect instances as well, I believe. ODS namespaces are applicable to HealthShare Unified Care Record instances and sounds like it's not applicable to your situation.
go to post Jenna Poindexter · Oct 20, 2019 Neerav- I'm not sure that you can. From within a production you can call from one host to another, e.g. bs->bp, bs->bo, bp->bp, bp->bo, bo->bp, bo->bo, etc. From outside the production you cant really call a bp or a bo directly. Why do you not want to setup a bs that can route your call to whatever bp or bo you want?
go to post Jenna Poindexter · Oct 19, 2019 From a business host you would use the ..SendRequestSync or ..SendRequestAsync method call. From outside of a business host you could create a business service that took a target configname and a request message as input and use the CreateBusinessService method in End.Director to iinstanciate and call it
go to post Jenna Poindexter · Oct 11, 2019 Stephen With regard to the name, it's just that, a name. It doesn't have any effect on what the production can and cant be used for.
go to post Jenna Poindexter · Oct 11, 2019 You can use the foundation production as a router if you want, the difference is that in that scenerio you would be adding all of the components that you needed to the production manually. Configuring a routing production should give you the basic components needed, e.g., a service for input, a router for applying rules based routing and then an operation. It provides the basic building blocks needed to route messages. A generic interoperability production can route messages as well.
go to post Jenna Poindexter · Oct 10, 2019 A foundation production is a production that is created using the Install Wizard and when created will include some useful business hosts for integrations
go to post Jenna Poindexter · Oct 10, 2019 StephenAn Interoperability production is a general integration production, vs a routing production is one that automatically includes some basic business hosts needed for routing messages. Typically you would use a routing production if you wanted to route HL7 messages, for example. An Interoperability production is a blank slate allowing you to add whatever business hosts you need. There is no real difference in capabilities other than what is automatically created as part of the production configuration when it is first created
go to post Jenna Poindexter · Oct 1, 2019 I would think that would depend on a few things. 1. What is the size of files being sent? 2. How much bandwidth is available to handle multiple concurrent transfers 3. How many connections can the remote ftp server handle?
go to post Jenna Poindexter · Sep 30, 2019 Hi This can happen when you are doing class based CSP coding and forget to add the #(..HyperEventHead())# call to the header of your document
go to post Jenna Poindexter · Sep 23, 2019 I would recommend getting your journal drive fixed, taking a full backup of your databases and then start journaling from there. Whether or not you need the journals depends on how you might be using them Obviously they are used to recover your databases since the last backup . They are also used for shadowing and mirroring
go to post Jenna Poindexter · Sep 22, 2019 What kind of error do you get when you try from a browser. From a browser URL the method is Get. Is your service Method a Get? Could also be licensing.
go to post Jenna Poindexter · Sep 4, 2019 You could throw them out into a file and then use an external diff tool.Jenna