Team Medevac (Medical Project)

Calls to CAMMS/Publisher from CAMIS

• Assign a file number to an initial applicant

• Add an assessment to a MER

  • Update status of work item to reflect assessment.

  • PBI 173581: Auto-update work item status when assessment is entered (fit/unfit)

  • PBI 173582: Auto-update work item status when assessment is entered (defer)

• Delete an assessment from a MER

  • Status of work item is reverted back to status prior to when the assessment was added.

If publisher goes down, any call from CAMIS during that time is lost
> updates in CAMIS are blocked when down, error message is shown

If eMER listener goes down, message doesn't reach it
> will retry when it goes back up

If APIs go down
> eMER listener will re-attempt 60 times every 2 minutes (essentially retries for ~2 hrs)
> set in appsetttings.json (see Task 232346)

Documents can be shared with applicants and/or CAMEs through CAMMS-SMMAC. Users have the option to notify the receiver through an email (via GC Notify).

When a document is shared, a new row is created in the document share table and if it is unshared, then the deleted date is set. If the doc is shared again, a new row is created.

The most recent notification date is set in this table and a history of all past notifications is logged in WA005.

The following actions are logged:

When a file number is associated with an MBUN

• process_name_nm: CAMIS-SIMAC-API.RegisterToken

• Updating file #_ MTOA/MBUN token from _ to _

When a document shared notification is sent out

• process_name_nm: CAMIS-SIMAC-API.UpdateDocShare

• Updating Notification of Document Share: [ ID: _, Document ID: _, Notified Date: _, Notification Email: _]

Unable to clear Bring Forward date if use clear button of calendar widget.
In order to delete/clear the BF date of a request, the user must use the delete/backspace key to remove the date from the field and then save. If the calendar widget’s clear button is used, the BF date will not be updated to null.
Bug 257385: Cleared/deleted BF Date in CAMMS Request doesn't save

When creating/updating a request, it cannot have the same date as an existing MER.
This is due to a constraint in the CAMIS database on UA006.
PBI 214783: Error handler - MER Date already exists