go to post David Marcus · Jun 5, 2021 I see ##class(HS.Util.Installer).InstallBusDemo in HealthShare_UnifiedCareRecord_Insight_PatientIndex-2021.1-1009-0-win_x64.exe What kit are you using? Of course, you should not be copying parts of the product into another instance.
go to post David Marcus · Nov 28, 2020 I'm not sure what you are asking. Transactions are for saving to disk. The methods I referred to just load the SDA into memory.
go to post David Marcus · Nov 27, 2020 You can use an XML editor that can validate XML against a schema. You can get the schema via ##class(HS.SDA3.Container).ExportXMLSchemaAPI. You can call GetNextSDA in a loop like ##class(HS.SDA3.Container).TestXMLParse does. But, I don't think this will catch datatype validation errors. To catch those, you could use ##class(%XML.Reader).Correlate.
go to post David Marcus · Nov 12, 2020 You can use the HS.Gateway.ECR.PatientDelete class. https://docs.intersystems.com/hs20201/csp/docbook/Doc.View.cls?KEY=HEMAP...
go to post David Marcus · Jul 10, 2020 Check the Ensemble Credentials in the HSSYS namespace on the Edge.
go to post David Marcus · Jun 18, 2019 I have an internal PowerPoint from someone who should know that says Summary Document Architecture. And the HealthShare docs says Summary Document Architecture.
go to post David Marcus · Mar 21, 2019 You can use the CDA and SDA Annotations. Check the "SDA" check box, then enter the SDA property you are interested in. See the documentation CDA Interoperability with SDA > CDA and SDA Annotations .
go to post David Marcus · Jul 9, 2018 In Clinical Setup > Chart Book Definition, select your chart book. On the Chartbook Setup page, there is a "Collapse Timeline" check box.
go to post David Marcus · Mar 28, 2017 I discussed this with Matt via email. The problem was due to custom code that expected the session ID to still be there after it had been deleted.
go to post David Marcus · Nov 15, 2016 Customers often have many systems, e.g., they may have live, stage, or dev environments or be testing a new version, so unfortunately it isn't reliable or practical for us to keep track of a customer's version. HealthShare also has multiple components, which may be upgraded separately.
go to post David Marcus · Nov 9, 2016 It might help if you were more specific. What do you mean by "attach"? How are you going to retrieve the documents? Where are the documents coming from?
go to post David Marcus · Nov 1, 2016 Yes, it will go back. But the query plan appears to show that it ignored the index. Why not use the index to determine which rows to get from the master map? Maybe it doesn't realize that this will be much faster?
go to post David Marcus · Oct 12, 2016 The HealthShare documentation is not on docs.intersystems.com, so you can't use Google. In HS Core 15, open the documentation, then click on "Roadmap to Implementing an Information Exchange", then click on Chapter 6, "Supported APIs". Before the name change, the book was called "Roadmap to Implementing a HealthShare Regional Solution" and the supported APIs were in Section 5.5. Searching for "Supported APIs" should also work.
go to post David Marcus · Oct 11, 2016 Hi, Scott."HealthShare" is no longer a particular product. Now it describes a family of products. What used to be called "HealthShare" is now called "Information Exchange". David said he has an Edge, so he has Information Exchange. We don't support querying tables for several reasons. Tables are internal to the product (unless explicitly documented otherwise). The APIs are documented in Roadmap to Implementing an Information Exchange> Supported APIs.
go to post David Marcus · Sep 27, 2016 What are you trying to do? Select the patients that only have certain kinds of data?
go to post David Marcus · Sep 19, 2016 I would read the index to find the records to output. The optimizer doesn't do that?
