Write Connectathon Synopsis

[briansok71]

What went well
• All Connectathon testing was done using the CDC subscription.
• Successful authentication of HDEA using IG option 2 (stored public key on server).
• Successful implementation of $process-message endpoint.
• Successful ingestion of FLU bundles into FHIR/Data Lake.
• Successful ingestion of HCS bundles into FHIR/Data Lake.
• Successful demonstration of PowerBI/Synapse heap map of a simulated Flu Outbreak through FLU bundle ingestion from HDEA to FHIR and downstream to Data Lake.
• Successful exchange of invalid bundles with OperationOutcome responses.
• Operational dashboard enabled visualization of activity, and enhanced our ability to troubleshoot and resolve issues quickly.
• Positive collaboration across team & participants throughout testing.

What didn't go well
• Last-minute code changes due to changing requirements in FHIR functions before Connectathon were not able to be tested thoroughly.
• General instability with the HDEA submitter app requiring redeployments and server restarts.
• The FLU & HCS bundles created by HDEA app would not validate against the IG resource profiles in HDEA app, so validation had to be disabled when ingesting into FHIR service.
• Our ability to toggle validation in $process-message was missing & had to be resolved with a quick code change and redeployment.
• The process of creating invalid bundles by participants during Connectathon was cumbersome and had to be done manually via email exchange.

What can we do better
• We need clearer requirements around the FHIR bundles and their associated IG resource profiles to be tested during future Connectathons.
• We need to test HDEA and CDC FHIR connectivity for Connectathon sooner so the team has more time for robust integration testing.
• The HDEA application needs to be updated to generate FLU & HCS bundles that can validate successfully against IG resource profiles.
• The HDEA submitter application needs improved stability before next Connectathon.
• We need better test cases and unit testing of the Azure Functions used by the FHIR solution.