prime-simplereport
prime-simplereport copied to clipboard
CDCgov
AIMS Integration
Outcome: SimpleReport users are able to report tests vai AIMS
Requires HL7v2 messages.
Work to be done
- Generate HL7 messages
- Store s3 credentials securely
- Validate HL7 against AIMS validator
- Send HL7 messages to AIMS (create queue and function app to get data to S3)
- There’s still work to get responses to us as messages work through the AIMS ecosystem.
- Start gathering requirements around Device and AoE data from STLTs
- Build communication plan around ^
- Timing around communicating to non-pilot STLTs that they can expect to receive reports from pilot jurisdictions (a Nevadan gets tested in IA for example)
- Data could take a different shape (depending on the requirements we put on our migration)
- How might we anticipate the change (if any) in experience for STLTs?
- They’ll likely lose device data and AoE data
There's additional work to pivot legacy SimpleReport from RS to AIMS: ⬇️SUPPORTING LEGACY⬇️
- Additional HL7v2 mapping (Add support for AoE and device data)
- Re-pipe Bulk uploader to point to AIMS
- What does reporting back to the user look like (for example when a record in the middle of a bulk upload fails)?
- CSV File format: For .CSV file transformation, it must be in the national flat file format. In the attached .zip file, the file "NatELRFlatFile_GapAnalysis_HL7Generator_20210129.xlsm" includes the appropriate headers on the "FlatFile_Result_Use" tab.NatFlatFile_HL7GeneratorTool-package-for-distribution_20210129 (1).zip
And additional Non-engineering work:
- How much communication do we need to do with STLTs to let them know this is coming?
- This isn’t really in our communication plan
- Theoretically we shouldn’t need to tell our users
- AIMS might have coverage beyond RS. Will this support jurisdictions who start receiving results?
Outstanding Questions
- Recommendation and decision document
- How integrated with/dependent on is the AIMS pivot with the pilot? Meaning, when we pilot, will the pilot data be sending through AIMS and the existing experience still connected to ReportStream? (Preferred way for me (Jeanette) would be moving everything to AIMS as soon as possible (especially because it shouldn't change the provider experience), just not sure what's interconnected and dependent and possible)
- Are all jurisdictions currently receiving data from us via Report Stream onboarded to APHL?
Held a kickoff call with APHL 5/17
Diagram from our kickoff call Assuming reporting through AIMS is part of the pilot scope, that means blood lead is no longer an issue.
