FAQ

Q: If I need to reload transfusion data, what do I do?

A: Perform three steps:

1. Truncate the BloodTransfusion and the BloodTransfusionHistory tables.

2. Repopulate the BloodTransfusion table.

3. Execute the PBMtoDM stored procedure.

Q: If I need to reload component results data, what do I do?

A: Perform three steps:

1. Truncate the ComponentResult and the BloodTransfusionHistory tables.

2. Repopulate the ComponentResult table.

3. Execute the PBMtoDM stored procedure.

Q: How do I reload dictionary data tables? (BloodProduct, Facility, Location, PatientType, Provider, Specialty, Test.)

A: Since the dictionary tables have foreign key constraints to the BloodTransfusion and, sometimes other dictionary tables, any table that has a dependency the dictionary table to be reloaded, as well as the BloodTransfusion and BloodTransfusionHistory tables, will need to be addressed.

1. Truncate the BloodTransfusion and BloodTransfusionHistory tables

2. Delete data from any other dictionary tables with a dependency on dictionary table to be reloaded, if any.

3. Delete (preferred over truncation) existing rows from dictionary table to be reloaded.

4. Repopulate dictionary data.

5. Repopulate BloodTransfusion table.

6. Execute the PBMtoDM stored procedure 

Q: I am not seeing Mass Transfusion – why is that?

A: Mass transfusions are defined in Accumen PBM Analytics as 10 or more RBC units ordered within a rolling 24 hour period. All Hem/Onc and RBC Exchange patients are excluded from Mass Transfusion counts.

Q: The Location Table is department level detail. We have a higher level grouping as Location ID, but we are skipping it per notes on Specs file. We don’t use LOC ID internally much either. Is this expected for Epic?

A: In Epic this is department level - the roll ups for Departments to "Locations/Regions" or however you want to group them is up to your hospital system. LOC_ID is a suggested column, you may need to use something else. This could be the department or location level depending on your EMR. 

Q: We have Specialties but no Specialty groups. What should we do?

A: The specialty groups are provided. Someone on the clinical side will need to tell you how to group the specialties.

Q: Specialty group is not available in our EMR data. What should we do?
A: The specialty groups are provided by Accumen in the Lookup_SpecialtyGroup table as pre-populated values. You will need to have your team provide mapping from your specialties to the pre-populated values in the Lookup_SpecialtyGroup. 

Q: Can the Providergroup column be null?
A: This can be NULL 

Q: Does the ProviderSpecialtyKey include first specialty linked to the provider?

A: Yes

Q: Does the ProviderSpecialtyOverrideKey include 2nd specialty linked to a provider?

A: No, this should be populated if you want to use a specialty that differs from the 1st one, but do not want to overwrite the first one. This can be NULL if using the 1st specialty. 

Q: We have Blood Products but no Blood Product Types roll-up. What should we do?

A: Pre-populated values come in this table and Blood Products are mapped to those. These values must remain static because they are used specifically downstream. If these are changed the downstream metrics will not be correct.

Q: BloodProductType is not available in our EMR data. What should we do?
A: The BloodProductTypes are provided by Accumen in the Lookup_BloodProductType table as pre-populated values. You will need to have your team provide mapping from your blood products to the pre-populated values in the Lookup_BloodProductType.

Q: It shows Test ordered…highest level grouping of tests (EAP records), right?

A: This is a grouping for analytes (components of a test) - one level down from the orderable tests. This is based on the component results. This is similar to the lookup_groups above. We provide the lookup values that TEST (component result codes in this case) need to be mapped to. This allows several hemoglobin result components (in-house, send outs, POC testing) to be mapped to one HGB Test Group. This allows for the correlation of results/groups to transfusion. 

Q: Min and Max values are not available at the Component level, but part of actual patient data where same test can have different reference values for min and max, apparently depending upon the patient details, for example – age or gender. How do I handle this?

A: This is used to enable out of range values to be excluded. There are suggested defaults provided in the instructions. This is a required field; however, it is not necessary to be tied to gender/age of the patient. This is to exclude outliers if desired by your hospital system. 

Q: Can a test roll up to more than one test group?

A: For the PBM data this tables is at the analyte level. An analyte can roll up to more than one Orderable test, but that does not roll up to more than one TestGroup in the database. For example - Hgb is included in several orderable tests; however, it maps to HGB and only HGB test group 

Q: TestType – allows for Panel or Component – We are presenting Panel level information, should this field say “component” as noted in the Data Definitions?

A: For the analytics being implemented for PBM, this needs to be set to “Component” because you are grouping at the component level. This table for PBM data is used for component level - not ordered test level.