Hi Scott -

Part of this depends on "how" (from what context) did you create your "export"

Assuming that you mean that you created an "export" from the System Management Portal:

Then review the documentation that can be found:


which will talk about the "Deployment" process for an "exported production"

Assuming that you are talking about an "export" from Studio, then the specifics of how a Business Operation is configured will be in the class definition of the Production Class (along with the actually configured Business Service/Operation class definitions (if they aren't standard InterSystems provided classes : i.e. If you have created your own FTP Operation class as opposed to using the FTP operation class InterSystems ships with the product)):

Then in this case you are looking at a more manual code promotion process, which involves importing from within Studio and recompiling things. This methodology is can work, but has a lot more moving parts (and therefor more "gotcha's" to look out for)

When you are using the Text Categorization, you need to have a piece of meta data that is used to group the text into different categories. "Gender", or "Month" or, "Diagnosis Code", etc.  Then each record has to have one of these values associated with it, so the learning process can determine what concepts/terms go with which category.

You will get the "category 1 covers the whole data" error, if you don't have a meta field either defined, or correctly populated. Without some level of variability in the "category" identified meta data field, the machine learning doesn't have reference point to sort out your text records.

Make sure that you both HAVE a Meta-Data element defined, and that there are differing values within the record set that you are using to create the categorizations.

Just out of curiosity, which part of HealthShare are you running these queries? Are you looking on the Access Gateway, Edge Gateway, Registry?

They all use the same message structure, but in different parts of the "request/response" cycle. The "facing the outside world" context is the Access Gateway, the rest are more "internal to Information Exchange" propagating of the request and motivating the various parts to gather the response, so it's quite likely that (as Justin mentioned) there can be replications of the message content into "new message" records that are NOT actual "new requests".

When you look directly at the SQL table outside of the context of the complete message trace (i.e. a "Session") it should be expected that you will see what appears to be exactly the same content in multiple messages in the table.

Hi Scott -

Have you looked at the Report Management framework under the Registry Management

(System Management Portal -> HealthShare -> Registry Management)?

Both the "Management Report" definitions, and the "Patient Report" definitions are a good starting point for some things. (Take a look at /csp/docbook/DocBook.UI.Page.cls?KEY=HERPT_ch_management_creating#HERPT_C273872 in the docs of your HealthShare installation)

"Response times" can be a bit tricky, since this is a measurement that would be not something that happens at a single point in the system (i.e. multiple Access Gateways, each having their own "start/stop" events, but only their own)

Hi Scott -

A little context might help us help you ;)

Are you talking about operational metrics? (i.e. How much work is my system(s) doing?, How fast are my journals growing? etc.) or are you talking about "What's Stakeholder X's traffic today and of what type?"

There are some MANY things available, it becomes a question of what is the purpose of the measurements so we can figure out where to start getting meaningful values for your business need.