1 minute reading time (207 words)

How to build an effective 340B Data Integration Solutions - Part II

I was wondering why should I lean towards the multiple episode of 340B Integration solutions.  It was one fine morning, received a few phone calls from the customer about the data corruption.  They got really panicked because it was end of the month and monthly invoice generation should have been completed.  when they reach out to me,  I didn't have any clue about the issue.  However I pacified them by stepping into the problem.  Customers have a fair confident about my knowledge and skills when it comes to fixing data issue.  

After spending a few hours to do the root cause analysis,  it was actually a simple data formatting issue have caused the huge problem.  Their data integration process was written directly on top of the source data which is in comma separated format(.CSV).  Some of the fields value has comma inside that triggers the cause because the ETL process split the data value into multiple column values. It appears to be a very simple problem but when it comes to do data loading process,  this would be major problem.  This potential problem could have been avoided if they have performed a data profiling or data cleansing before loading the data into the target tables directly.

How to build an effective 340B Data Integration So...
HRSA Regulatory Update for 340B Program
 

Comments

No comments made yet. Be the first to submit a comment
Already Registered? Login Here
Guest
Tuesday, 10 December 2019
If you'd like to register, please fill in the username, password and name fields.

Captcha Image