Search

\E\fs20\E\b Patient Name: \E\plain\E\f6\E\fs20 {\E\v<%NAME%>}ZZZPORTAL TWO, DO NOT TOUCH{\E\v<%END%>}\E\line\E\plain\E\f6\E\fs20\E\b Date of Birth: \E\plain\E\f6\E\fs20

you call the method, because the Args(index) should be a number, but not a meaningful parameter. Guys, thanks for a lot of options! It looks like it is a relevant question

, and running "Cleanup SQL Statement Index". But on earlier releases they seemed to be removed more often. At a live site it is reasonable to expect that the statistics

="GET" Call="Index"/></Routes>}ClassMethod Index() As %Status{ write "I am installed!" return $$$OK}}Once the class is created and compiled, we need to register

tSC } In the above code, note that pClassName refers to the table containing the data we'll be indexing, and not the current class. We then create a read-only class

of a global reference is limited to 511 encoded characters [1].4. Class Limits:o Inheritance depth: 50o Foreign keys: 400 per classo Indexes: 400 per classo Methods

. The development portal makes it easy to get started to learn and test FHIR queries – I encourage you to check it out. FHIR resources such as Patient, Observation, Diagnostic

": "POST", "url": "Patient" } }, { "resource": { "resourceType": "Patient", "id": "evn", "identifier

to use wildcards for storing same data structures in different named tables, or playing with indexes. And relating to this I have found a problem in classes I don't know how to get

, or turn them into a $LIST and reference the elements by numeric index. The only delimiters you'll need to set for the record map are a "|" as the field delimiter

Indexing. I also have heve very long ID's in the form: {InterfaceName}||{NameSpace}||{RowId} So, at this point I have a couple of different approaches that use Class and Global

in the main bottom widget, you can click the eye icon to consult the complete source text and optionally highlight indexing results or dictionaries (more on the latter in future

+----------------- attribute values ------------------| %changed = 1| %data("MyProp") = 22| %index = ""Stored : 1@%ZEN.proxyObjectGot : 1@%ZEN.proxyObject'1@%ZEN.proxyObject

and as they grow in number proportionately the disk usage will increase. The disk space usage will not be only from the message body data, but also from any indexes/search table

with the series on [Caché capacity planning and performance](https://community.intersystems.com/post/intersystems-data-platforms-capacity-planning-and-performance-series-index) I will use