Dendi Inc. - API Sender Onboarding

BerniXiongA6 commented 1 year ago

What You Need to Know

[ ] Terms of Service agreement signed
[x] Kickoff meeting completed
[x] Company’s intake form: [paste info below this]

Background Information:

Name: Lizzie VanSword Job title: Product Manager Organization: Dendi, Inc. Email address: integrations@dendisoftware.com Phone number: (205)616-0357

Public health department(s) I report to: all states listed and a few not listed Current reporting method(s): CSV to each state

We would be providing this service to all of our labs that we currently operate as the LIS for.

What is your expected daily message volume? 5,000 tests daily Are you currently reporting to any other states? Our clients report to AL, CA, GA, CT, FL, IL, KY, LA, MD, MO, NC, NE, NJ, NM, NY, OH, TN, TX, VA, WV What is your current process for reporting COVID-19 data (I.e. CSV, HL7)? CSV File upload by each lab

To Do

[ ] create individual tickets for this epic
[ ] RS team member who originates this ticket: complete the following when creating this Issue.
[ ] RS team member who originates this ticket: add any dependencies, as needed

sliu1000 commented 1 year ago

Update from Sender:

Hi James,

We plan to use the 2nd Connectivity option, using the shared secret API key. Please generate a secret key and send it via encrypted message. Dendi LIS will use that secret key with each submission. Best regards,

Shatabdo Banerjee dendisoftware.com

sliu1000 commented 1 year ago

Updates:

Hi Shatabdo,

Before we look at the files, I'm not seeing any attempts to hit the production environment from dendi in the logs. I do see a couple of 400's in staging. Can you verify that you are trying to send to the production environment at prime.cdc.gov/api/waters or prime.cdc.gov/api/reports? Please ensure that we do not send real data to the staging environment.

example curl command for production:

curl -X POST -H “client:dendi” -H “content-type:text/csv” –data-binary “@./dendi-PII- data.csv” -H “x-functions-key: ” https://prime.cdc.gov/api/waters

The error I am seeing in staging is that there isn't a match for column "equipment_model_name" which should match with the appropriate value from column B from the CDC SARS-CoV-2 LIVD Table (https://www.cdc.gov/csels/dls/livd-codes.html). The other errors appear to be stemming from this one as we do a lookup based on that value to populate other fields.

If you are trying to hit the production endpoint and it's not registering in our logs that's a different issue and if that is the case you can share the error message you are getting back with me via keybase (jgilmorea6) or encrypted email.

Thanks,

James

James Gilmore (Agile Six)

Sent: Monday, April 17, 2023 11:22 AM To: Gilmore, James (CDC/DDPHSS/OD/HITSSU) uaf6@cdc.gov Cc: Report Stream (CDC) reportstream@cdc.gov; Brandon Canniff brandoncanniff@navapbc.com; Dendi Integrations integrations@dendisoftware.com; lafredahoward@navapbc.com lafredahoward@navapbc.com Subject: ReportStream / Dendi: Production environment files

Hi James,

We tried sending production files, but encountered multiple errors. How can we share the files securely, to review?

Best regards,

Shatabdo Banerjee dendisoftware.com

On Wed, Apr 5, 2023 at 8:00 AM Shatabdo Banerjee sbanerjee@dendisoftware.com wrote: Hi James,

We should have some files queued up for next week.

Best regards,

Shatabdo Banerjee dendisoftware.com

On Tue, Mar 28, 2023 at 1:43 PM Gilmore, James (CDC/DDPHSS/OD/HITSSU) uaf6@cdc.gov wrote: Hi Shatabdo,

File was received and everything looks good. If you are ready, I would like to move on to the last step of onboarding which is for you to send a few real examples to our production endpoint. We will use those examples (3-5) to validate with the appropriate public health jurisdiction and once they give the green light we are good to move to full production mode.

Please ensure that any real patient data is sent to our production endpoint (prime.cdc.gov/api/waters) and that no real data is sent to the staging environment. Please let me know if you have any other questions or require further validation in the staging environment.

Thanks, James

sliu1000 commented 1 year ago

Update from Sender:

Hi James,

We tried to send the file to production and received the following errors. "errorCode": "INVALID_MSG_PARSE_CODE" - for field patient_race (patient_race) - this maybe related to "Other Race" "errorCode": "INVALID_MSG_EQUIPMENT_MAPPING" - this is named as "Accula SARS-Cov-2 Test* " Please let us know how we need to update these items and re-submit the file?

Best regards,

Shatabdo Banerjee dendisoftware.com

sliu1000 commented 1 year ago

Update from Sender:

Hi James,

We have submitted another file [NPI fix + Out of state patients] . Please review and let us know :

"id": "362f066f-ae2e-4e81-927e-bdb33ca60421",

"submissionId": 24096910,

"overallStatus": "Received",

"timestamp": "2023-05-08T16:18:31.404Z",

Best regards, Shatabdo

sliu1000 commented 1 year ago

Update from Sender:

We sent the file today and received an error message. Please let us know the issue? The COVID LOINC code is https://loinc.org/94500-6

"id": null,
"submissionId": 24247993,
"overallStatus": "Error",
"timestamp": "2023-05-25T14:16:08.343Z",
"plannedCompletionAt": null,
"actualCompletionAt": null,
"sender": "",
"reportItemCount": null,
"errorCount": 124,
"warningCount": 372,
"httpStatus": 400,

Error rcvd -

"field": "test_performed_name (test_performed_name)",

"message": "No match found for test_performed_name (test_performed_name); please refer to the CDC LIVD table LOINC Mapping spreadsheet for acceptable values.",

"errorCode": "INVALID_MSG_EQUIPMENT_MAPPING"

CDCgov / prime-reportstream

Dendi Inc. - API Sender Onboarding #7582

What You Need to Know

To Do