Ah, I should mention that this is happening in code that I can't access.  I can't really tel what's going on except by looking in the database after it's all "said and done". I can try that with one particular row in the database, but it's happening upstream, in othercode, and I'm wondering now if it's because the other code is possibly saving the Claim object differentlly.

However, this is a good idea.  I'll play arond with a couple of objects that are already in the database, and se if I can save them to be "right side up", and then "upside down" again.

I can't use

Select claim.ClaimNumber, line.ProcedureCode from Claim
JOIN ClaimLine line ON claim.ID = line.Claim

because there is no line.Claim value.

I found the other method that needs to be overidden.  It's the XMLImportSDAString method.  This method was already making allowances for the "%" character for the HS.SDA3.CodeTableDetail.UoM class, so I follows the example and added my valid characters when it's importing SDA for the HS.Local.SDA3.CodeTableDetail.xProcedureModifier class.

Hi Harshdeep,

It's not something I read so much as figured out the hard way.  But here is the link to the HS.SDA3.CodeTableDetail.CareProvider object:


Which says, "In the Viewer Cache, CareProviders are matched on Code, SDACodingStandard,
Description, and CareProviderType (which is itself a code table). Other
properties are updated if different."

I think that the "matched on" properties are required in order to store the object.  So, setting a Name, but not a Code, will not store the object (this was my example).

As for the properties in FHIR that will map to the necessary SDA properties... you'll have to find the Schema Documentation for FHIR, on your instance's System Management Portal. I think that will be under HealthShare / HealthShareManagement  / Schema Documentation / FHIR Annotations. 

Possibly that will help.

Can you show an example of the data getting removed?  If it's something like Provider.Name_FamilyName, then it might be removed because there's no corresponding Provider.Code.  Some objects are not set into SDA unless the properties used for matching are included.

We also set the HS.Facility.Config Tier property as well, in HSREGISTRY, to a large number.  Would this affect how information from different edges is rated when getting fed into HSHI?  Is this an acceptable use of this property?



Note: we already set the <trustedTier> of the Facility in question to a large number (so, lower priority) so that the Composite information uses other data from other Facilities, instead of this Facility.  This affects the composite record in HSPI.

I assume HSHI /Analytics is not tied to this?


Using Ensemble 2018.1.2, I'm using the pInput.Attributes("FTPDir") to get the full difectory of the filename (where pInput is %Stream.Object) when I have a root directory defined (e.g. /send) and the property Subdirectory Levels = 2.

I also, was trying to find a way  to use the subfolders of the file that's on the server to either run a rule or more simply, create the same folders on our side.  When the production service uses Subdirectory Levels, this subfolder information is not part of the ..Adapter.FilePath (e.g. the root folder is /send, the file is /send/sub1/sub2/testfile.txt, Subdirectory Levels=2, but the Adapter.FilePath = /send/testfile.txt)

However, using the FTPDir attribute of the %Stream.Object gives me the full directory of the source object, from which I can "piece" together appropriate storage path on our end.


Hi Keith, I am sorry! In a SQL database (MySQL, Oracle...), is there a way to drop a table (not a view; a Table) without deleting data?

If you really want to remove the SQL table but keep the data, you can merge the global that stores the actual data into a diffefrent global, such as merge ^SavedData = ^Package.TablenameD (You have to find the right global name from the Storage in the class).

This could take a few minutes to complete. Then you can delete the class.  I don't recommend this.

I suggest you contact IS to help you create a table definition that can be indexed, and perhaps populate this new table with your current data - perhaps a new table will be more efficient. IS is very helpful when it comes to support. And, let us know how it goes!