Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Washington - UP Migration - Validate Test Data #16629

Open
8 tasks
chris-kuryak opened this issue Nov 22, 2024 · 2 comments
Open
8 tasks

Washington - UP Migration - Validate Test Data #16629

chris-kuryak opened this issue Nov 22, 2024 · 2 comments
Assignees
Labels
engineering Work to be completed by an engineer needs-refinement Tickets that need refinement from the team onboarding-ops Work related to onboarding with a partner. Addressed by the Onboarding & Operations team in RS. receiver Analytics label to flag work related to State/Receiver/STLT features

Comments

@chris-kuryak
Copy link
Collaborator

Washington = name of STLT

User Story:

As a developer, I want the [STLT] to validate test messages in staging, so that they can receive data in the format they expect.

Description/Use Case

[STLT] is already receiving data from the covid pipeline they will be onboarded to the UP where they will be receiving data from SimpleReport including Covid, Flu and RSV. We need to make sure the message we generate from the UP passes the STLTs validation. We can use SimpleReport to submit test messages to the STLT.

Risks/Impacts/Considerations

  • WA has not fully responded to our questions yet. So start with getting them set up for COVID, but don't send any test results until we get responses to all of their questions.

Dev Notes:

  • Upload the newly created receiver settings to Staging
  • Copy the receiver's secret key with the new receiver name in Azure's staging environment
  • Verify we can connect to the newly created receiver
  • Send a test message through Simple Report and make sure it gets routed to the STLT
  • Send test messages according to the STLT needs

Acceptance Criteria

  • Created and sent data using Simple Report
  • Confirmed with STLT that data passes validation
  • When finished, tag Mikaelah, Chris, and Glenn in a slack post stating:

[STLT] "Testing in Staging" is complete and will be moving on to "Monitor in Production"

Connection Type: [REST, SFTP, SOAP, etc]

Conditions tested: [List of Conditions]

Positives set up to receive: [List of Conditions]

Negatives set up to receive: [List of Conditions]

Format receiving: [HL7 or FHIR]

@chris-kuryak chris-kuryak added engineering Work to be completed by an engineer needs-refinement Tickets that need refinement from the team onboarding-ops Work related to onboarding with a partner. Addressed by the Onboarding & Operations team in RS. receiver Analytics label to flag work related to State/Receiver/STLT features labels Nov 22, 2024
@abiphilipnava
Copy link
Collaborator

To clarify:
Convert Washington to UP (universal pipeline) into staging and change and syntax/functions into FHIR syntax and run a sample test to make sure the conversion has been completed. Correct?
High level Steps:

  1. Create a new branch from main and download existing code base.
    
  2. Make changes in WA.yml and organizations.yml 
    
  3. Send the changes into staging via command line.
    
  4. Log into staging.reportstream.com verify the changes.
  5. When the security pgp key (public/private) comes from WA , run the necessary steps and enter it into the UI
  6. Run a test.

Correct?

Abi

@victor-chaparro
Copy link
Collaborator

No, that work has been completed already. All we need to do is uploaded the existing wa-phd.yml to staging and test that transforms and FHIR path filters are working as expected. Do not route any messages to them. You can verify the transforms, settings, and filters are working as expected by going into their Daily data page and downloading the messages from there.
One thing I just saw is that they're one of the receiver that this settings enabled:

        convertPositiveDateTimeOffsetToNegative: true
        stripInvalidCharsRegex: null
        convertDateTimesToReceiverLocalTime: true

We're going to have to create an enrichment schema for them since those settings are no longer working in the UP.
@lucero-v can provide more guidance on that if needed while I'm out.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engineering Work to be completed by an engineer needs-refinement Tickets that need refinement from the team onboarding-ops Work related to onboarding with a partner. Addressed by the Onboarding & Operations team in RS. receiver Analytics label to flag work related to State/Receiver/STLT features
Projects
None yet
Development

No branches or pull requests

3 participants