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?
- Log in to post comments
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?
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?
There are various XSLTs in CSP\xslt\IHE\XDSb\Version1.
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.
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.
What are you trying to do? Select the patients that only have certain kinds of data?
I would read the index to find the records to output. The optimizer doesn't do that?
Why was the "SELECT COUNT(*) FROM MyCustomTable" fast?
It looks like ##class(EnsPortal.Template.filteredViewer).DoSearchSave is just saving them to the EnsPortal.MsgFilter.SavedSearch.cls table, which puts them in the ^EnsPortal.SavedSearchD global.
Please explain what you mean by "with database". You can save data to disk in Cache by assigning to a global, e.g., set ^Foo = "Bar".
What do you mean by "reset"? What exactly did you do?
See the documentation:
Overview of Health Connect
> CDA and SDA Annotations
/csp/docbook/DocBook.UI.Page.cls?KEY=FOVW_ch_cda_sda_annotations
This explains that you can find the schema documentation on an Edge under
[HealthShare] > [HSEDGE] > [Schema Documentation] > [SDA/CDA Annotations]
The UI isn't completely obvious, but the docs do give some explanation.
I believe the correct statement is that Rdratio is the ratio of logical block reads to physical block reads, but is zero if physical block reads is zero.