Skip to content
This repository has been archived by the owner on Feb 7, 2025. It is now read-only.

CA: CDPH Results Staging Connectivity #834

Closed
11 tasks done
sfradkin opened this issue Jan 31, 2024 · 6 comments
Closed
11 tasks done

CA: CDPH Results Staging Connectivity #834

sfradkin opened this issue Jan 31, 2024 · 6 comments

Comments

@sfradkin
Copy link
Contributor

sfradkin commented Jan 31, 2024

Story

As CDPH, so that NBS findings can be distributed to CA hospitals connected to ReportStream, I need ReportStream staging to be able to collect results messages.

Pre-conditions

  • Out of scope: production connectivity
  • ReportStream/TI already supports SFTP ingestion of results messages

Acceptance Criteria

  • A sample ORU message placed in the test SFTP directory is collected and ingested by ReportStream staging.
  • Results messages are transmitted securely.

Tasks

  • Receive test SFTP credentials using a secure connection
  • Test collection via SFTP
  • Test decryption and decompression of message files
  • Ask of CDPH if TN data type (post discharge provider telephone number), instead be sent as ST, TX, or XTN (learned on 8/7 that related OBX not sent)
  • Register public key for SFTP
  • Test removal of files after collection
  • Configure a sender for CDPH (or is this for the SFTP ingest service?)
  • Testing staging connectivity for SFTP ingest via REST
  • Test end-to-end flow

Research Questions

  • Optional: Any initial questions for research

Decisions

  • Optional: Any decisions we've made while working on this story

Notes

  • Optional: Any reference material or thoughts we may need for later reference
@JohnNKing JohnNKing changed the title California: CA PHL to ReportStream CA: CDPH Results Staging Connectivity May 6, 2024
@sfradkin sfradkin added the result-from-lab for CDC mapping label May 29, 2024
@JohnNKing
Copy link
Contributor

Blocked pending CDPH access and SFTP ingest work

@JohnNKing
Copy link
Contributor

To confirm:

  • Can TN data type (post discharge provider telephone number), instead be sent as ST, TX, or XTN?

@jorg3lopez jorg3lopez assigned jorg3lopez and unassigned jorg3lopez Jul 26, 2024
@JohnNKing
Copy link
Contributor

To confirm:

  • Can TN data type (post discharge provider telephone number), instead be sent as ST, TX, or XTN?

We found that TN would not be sent in actual results messages. (We tested and confirmed that's true even if the order includes a post discharge provider telephone number [as an ST data type, IIRC]). The TN we saw was just an erroneous artifact of the results generator web tool.

@JohnNKing
Copy link
Contributor

@JohnNKing To follow up with Stream 1; presumably this can be closed

@JohnNKing
Copy link
Contributor

@scleary1cs Was this one discussed during Stream 1 planning? Do you know if this can indeed be closed out?

@scleary1cs
Copy link
Contributor

I believe this can be closed @JohnNKing

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

6 participants