New Jersey - UP Receiver migration Pre-work

[chris-kuryak]

[STLT] = New Jersey

User Story:

As a developer, I want to compare the messages generated from the Covid and Universal pipelines, so that I can successfully onboard [STLT] to the UP

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 matches the Covid pipeline message.

Risks/Impacts/Considerations

Dev Notes:

• [ ] Fetch [STLT] organization settings from production and load them locally

• [ ] Use the attached SimpleReport covid postman collection and make sure the message gets routed to [STLT] locally. Modify the message to meet [STLT] filter if needed Simple Report Covid.postman_collection

• [ ] Make a copy of the [STLT] organization settings to onboard them to the UP. See How to Migrate an existing receiver to the UP documentation for more details: https://github.com/CDCgov/prime-reportstream/blob/master/prime-router/docs/onboarding-users/migrating-receivers.md

• [ ] Use this Postman collection to send a FHIR bundle the UP and make sure the message gets routed to the new UP [STLT] receiver. You may need to update the Simple Report sender to use the simple-report-sender-transform.yml if it's not using it. Simple Report UP.postman_collection

• To migrate the Covid translation settings start by looking at their current translation settings. If the receiver uses any of the following settings you will need to create a receiver schema:

  • receivingApplicationName
  • receivingApplicationOID
  • receivingFacilityName
  • receivingFacilityOID
  • messageProfileId
  • replaceValue
  • replaceValueAwithB
  • reportingFacilityName
  • reportingFacilityId
  • reportingFacilityIdType
  • suppressQstForAoe: true
  • suppressHl7Fields
  • suppressAoe: true
  • defaultAoeToUnknown
  • replaceUnicodeWithAscii
  • useBlankInsteadOfUnknown
  • usePid14ForPatientEmail: true
  • suppressNonNPI
  • replaceDiiWithOid
  • useOrderingFacilityName not STANDARD
  • receivingOrganization
  • stripInvalidCharsRegex

• More documentation on how to set-up these transforms in the UP will be provided, but for now you can look for examples on how to set this up in either the NY-receiver-transforms or CA-receiver-transforms

• If the receiver uses any of those transforms you will need to create a receiver transform under metadata/hl7_mapping/receivers/STLTs/ and update the receiver settings to point to this schema.

• After migrating the receiver setting to the UP. Send another test message using the postman collection or feel free to use the PrimeCLI to test the sender and receiver transforms using this command: ./prime fhirdata --input-file {PATH TO INPUT FILE} -s metadata/fhir_transforms/senders/SimpleReport/simple-report-sender-transform.yml --output-format HL7 -r metadata/hl7_mapping/receivers/STLTs/{RECEIVER SCHEMA} --output-file {PATH TO OUTPUT FILE}

• Compare the two messages again and document if there are any differences between the two messages. If there are review them with the team. We will probably need to ask the sender to add missing data or add a sender transform.

• [ ] Use a diff tool of your choice and compare the two messages generated between the two pipelines and document the differences. You can find an example here RI/SR UP vs Covid

• If there are no major differences we can move on to sending test messages to the STLTs staging environment.

Acceptance Criteria

• [ ] Created and sent data to [STLT] through the covid pipeline locally
• [ ] Created and sent data to [STLTS] through the universal pipeline locally
• [ ] Migrated Covid receiver translation settings to the UP receiver settings
• [ ] Successfully generated a message with migrated UP receiver settings
• [ ] Review transforms settings with the team
• [ ] Compared messages from the covid and universal pipelines and documented differences and review with team

[chris-kuryak]

@adegolier Have you started on this?

[adegolier]

NJ has truncation settings, which appear to not work correctly in UP. Bug ticket #14264 created to address.

[adegolier]

I pushed the branch up and I started to make a PR for it, but I'm having some weird test failures (unrelated since they're happening in master, too) and trying to figure out what's going on with that

[chris-kuryak]

Blocked by truncation bug

[chris-kuryak]

Truncation no longer blocking

[chris-kuryak]

Waiting on PR from Jessica to merge