Replies:

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:

https://docs.intersystems.com/irisforhealthlatest/csp/documatic/%25CSP.D...

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?

Thanks,

Laura

Followers:
Following:
Global Masters badges:
Laura has no Global Masters badges yet.