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.
- Log in to post comments
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.
Why was the "SELECT COUNT(*) FROM MyCustomTable" fast?
I would read the index to find the records to output. The optimizer doesn't do that?
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.
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.
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?
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.
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.
What do you mean by "reset"? What exactly did you do?
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".
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.
What are you trying to do? Select the patients that only have certain kinds of data?
There are various XSLTs in CSP\xslt\IHE\XDSb\Version1.
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?
Is journaling on?
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.
In Clinical Setup > Chart Book Definition, select your chart book. On the Chartbook Setup page, there is a "Collapse Timeline" check box.
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 .
I have an internal PowerPoint from someone who should know that says Summary Document Architecture. And the HealthShare docs says Summary Document Architecture.
I suggest you contact the WRC for help with this.
Check the Ensemble Credentials in the HSSYS namespace on the Edge.
You can use the HS.Gateway.ECR.PatientDelete class. https://docs.intersystems.com/hs20201/csp/docbook/Doc.View.cls?KEY=HEMA…
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.
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.
SQL uses single quotes for string values, not double quotes.
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.
You can find what is supported at
https://www.intersystems.com/products/healthcare-standards-certificatio…
By "HealthShare", which product do you mean? In general, we only have what is in the documentation. I'm not sure what you expect to be in a "support document".
I'm not aware of any logs. By the way, this question is about Unified Care Record, not IRIS for Health.
You need to look at the sync business operation in the Registry. That probably has a useful error message (if the request made it to the Registry).