Search

) in your narrative, but your code references PV1.3 (assigned patient location), so adjust the below as needed to identify the proper field: //create a copy of the request Set newREQ

a Better Experience for Both Patients & Providers Eduardo Conrado, Executive Vice President, Chief Strategy & Innovation Officer, Ascension InterSystems Healthcare: What’s New

://github.com/intersystems-ib/tool-patient-generator Hi @LuisAngel.PérezRamos ! This is great! If the project also available on OEX? Not yet @Evgeny.Shvarov, it's a bit basic and it's

Memorial Sloan Kettering Cancer Center — the world’s oldest and largest private cancer center — has devoted more than 135 years to exceptional patient care, innovative research

, for that matter). That's the thing, I don't want views, I want tables, and I need indexing (which was how this all got started, the indexing is not working). I was not aware

or a birthday from its index? kind of if i have search someone from its name and have all his information displayed This is a great question. In your example you haven't created

; the additional columnar indices work well in conjunction with them and are meant to avoid excessive reads from the master map or regular index maps (single gref per row). If your

. The Statement Index already records a rich set of metadata such as detailed runtime statistics and query plans for each statement, which typically has any literals substituted

and MSH:9 respectively). You should use IDs and other indexed properties such as SourceConfigName/TargetConfigName and Status to fetch the messages, then use HL7 Spy's powerful

%Persistent { Property Value As %String; Index IDKEY On Value [ IdKey, PrimaryKey, Unique ]; Method %OnNew(Value As %String = "") As %Status [ Private, ServerOnly = 1

definitions, because when i execute the second SQL on my classes and some random data, it will show the results i expect :(maybe you need to re-index your tables) Also check

.%GetMetadata().columns.GetAt(index).colName // and label. Notice that columns must be an instance of %ResultSet.MD.Column. Hi Rubens, Is this what you are after... set rs

"it will run every two days"? Or have I misunderstood something? If you have a flag on your database that you set after reading the records, and this flag has an Index, you should

property for it, even though that would make your life easier.First of all, for optimisation purposes, add an index on your list items:Index Bar On MyBars(ELEMENTS); Then use

is and there are "correct" indexes, the smaller the GREF and, accordingly, the shorter the execution time. But this is influenced by many factors, not just the above: see InterSystems SQL