eRSD Update

[robertandremitchell]

Description:

An update to the eRSD, which will add multiple conditions is due sometime in March.

Because there are added conditions, we will need to assess a few things:

• Confirm whether valuesets/concepts differ for existing conditions, in such a way we will need to start investigating ways to maintain "deprecated" valuesets or concepts. I think it is only if valuesets/concepts have been subtracted that we should have a problem.
  • If that is the case, we should have a new ticket to begin assessing how we ought to handle updating existing queries. In prior conversations, it sounded as though this would probably require updating the column in queries that holds the query data to JSONB to more effectively parse and manage updates to existing queries.
  • We would also still need to determine how in-flight / shipped versions of QC would receive this update, how to communicate it, etc. It may be worth doing this exercise / reaching out for user research regardless of whether we necessarily have to do it this go-around.
• Confirm whether this newest update has category data on conditions. This has not previously been present; if it continues to not be, we should confer with Dan to get the contact info of the person with whom he worked to get that info for the new conditions.
  • If we do have to reach out anyway, it may be worth asking them directly if they do maintain a more comprehensive changelog; I recall not being able to find one in the past but it could be good for us to have.
• Confirm our code works as-is given changes described. The other changes described do not sound as though they should break our existing code, but this would obviously become a high priority to either lock our existing version of eRSD rather than grab the latest and then work on any required updates.

Skylight Mail - Coming Soon_ March Release Electronic Reporting Surveillance Distribution (eRSD).pdf

Acceptance Criteria:

[linear]

QUE-183 eRSD Update

[robertandremitchell]

@janki to follow up with Dan about getting contact info for APHL contact so we can get updated category data.

Because we are not yet in production in any jurisdictions, we don't need to invest now in determining the best way to do this change logging. At most, our focus should be on ensuring that we get updated category data and that our code works as-is when the new update is deployed.