Info |
---|
A workflow management and medical assessment tool used to support the entire life-cycle of a medical report for licensed aviation personnel. Key functionality includes: |
System Profile
System Full Name | Civil Aviation Medical Information System |
---|---|
System Full Name (French) | Systeme d'information medicine de l'Aviation civile |
Subject Matter Expert | Michelle Coelho |
Web Team Expert | Michaud, Marcel |
Division | Medicine |
NTARS Code | CA09 |
Source Code Location (Archived) | |
Source Code Location | https://dev.azure.com/transport-canada/DSD-CIVAV%20Support/_git/CAMIS-SIMAC |
Technology Assessment
Platform Type | Web (Internal/Secure) |
---|---|
Database Platform and Version | Oracle 18C |
Development Language and Framework | ASP.NET + VB.NET |
Operating System and Version | Windows Server 2016 |
Additional Dependencies | |
Authentication | Entrust True Pass |
Environment Access Information
ENV | UNC | WWWFILES | URL | DB |
---|---|---|---|---|
DEV | \\tcwebscripts\tpwwwroot\eigdev\CAMIS-SIMAC | CAMISD | ||
PREACC | PREACC_CA | |||
ACC | \\tcwebscripts\tpwwwroot\eigacc\CAMIS-SIMAC | CAMISA | ||
TRAINING | CAMIST | |||
PROD | CAMISP |
Expand | ||
---|---|---|
| ||
PreAcc: http://catcpreaccpx.tc.gc.ca/Saf-Sec-Sur/2/camis-simac |
CAMIS Report Generator (CAMIS Weekly Auto-Accept report steps):
This program needs to be run weekly on Monday until the changes to CAMIS/eMER have been finalized.
System Overview
Info |
---|
To provide a secure method for the submission of electronic Medical Examination Reports (MERs) for licensed aviation personnel and supporting medical documentation to Civil Aviation Medicine (CAM). Its purpose was to keep track of these medical reports, provide automated approval or specialized scrutiny by CAM medical resources, and store tombstone information on Civil Aviation Medical Examiners (CAMEs). CAMIS Version 3.0 has been developed as a secure, thin-client, web-based, multi-tiered |
...
see Files for testing attachment types
Deploying CAMIS to development, acceptance and production: |
---|
How-To and Fixes
Info |
---|
Suggested credential for any fix: |
...
localhost
publishing packages for development, acceptance and production
...
Checklist for the business users to check first:
Account Access: CAME cannot access/login to eMER - preliminary troubleshooting for business
...
Account Access: CAME cannot access/login to eMER (developer troubleshooting)
...
Creating a CAMIS USER
Create 2FA admin account for CAMIS (for CAME and CAME associate account administration purposes)
Account Creation for access to eMER:
...
The difference between CAMES and CAME Associates
CAME Associates are generally nurses/admin staff within a CAME's office, who do some data entry on behalf of the CAME(doctor).
CAMES and CAME Associates access eMER the same way: with a GCKey and 2FA authentication.
...
Creating a CAME profile
Creating a CAME Associate Profile
...
Applicant merge
This is used for merging duplicate files. It is different from File Transfer
Merging duplicate applicant files
Incoming eMER lost after being accepted
Incoming eMER lost after being accepted.
...
Solution for oracle error when updating CAME profile
...
title | CAMIS/eMER Region Change |
---|
Required info: First and last name of applicant and their new region.
Within CAMISP.WORLD, in the table CAMIS.UA006_MEDICAL_EXAMINATION
, change the CAMIS_REGION_CD
to the requested region.
The region value list is available in CAMIS.TA057_CAMIS_REGION
. As of 2021-07-28, the region list is:
...
Code
...
Name (English)
...
431
...
Outside of Canada-Ottawa (HQ)
...
432
...
Quebec - Dorval (UL)
...
433
...
Ontario - Toronto (YZ)
...
434
...
Central - Winnipeg (WG)
...
435
...
Western - Edmonton (XD)
...
436
...
Pacific - Vancouver (VR)
...
437
...
Atlantic - Ottawa (QM)
...
3642
...
Overview of CAMIS User (internal) and eMER accounts
External (eMER) and Internal (CAMIS User) accounts are both added to AC040_STAKEHOLER because AC040 is the master account table.
-> External accounts are identified by STAKEHOLDER_TYPE_CD = 2
-> Internal accounts are identified by STAKEHOLDER_TYPE_CD = 1
Table AC043_INTERNAL_STAKEHOLDER is for internal (CAMIS User) accounts ONLY.
Table AC044_INTERNAL_STAKEHOLDER is for external (eMER - aka CAME Admin and CAME Associate Admin) only ONLY.
For a more detailed explanation of the accounts that are managed in CAMIS, please see,
Accounts that are managed in CAMIS
Account access issues:
CAME Accounts:
Checklist for the business users to check first:
Account Access: CAME cannot access/login to eMER - preliminary troubleshooting for business
Developer troubleshooting (queries)
Account Access: CAME cannot access/login to eMER (developer troubleshooting)
Account Creation for access to CAMIS:
Creating a CAMIS USER
Create 2FA admin account for CAMIS (for CAME and CAME associate account administration purposes)
Unable to generate new activation code for CAMES - BSD - Civil Aviation - Confluence (atlassian.net)
Account Creation for access to eMER:
Process for giving CAMES and CAME Associate Admins access to eMER on production.
The difference between CAMES and CAME Associates
CAME Associates are generally nurses/admin staff within a CAME's office, who do some data entry on behalf of the CAME(doctor).
CAMES and CAME Associates access eMER the same way: with a GCKey and 2FA authentication.
The processes for creating a CAME or CAME Associate profile can be used by developers for creating test accounts on development and acceptance but not Production as the names of developers are not supposed to appear in the list of CAMES in the existing CAME dropdown. |
---|
Creating a CAME profile
Creating a CAME Associate Profile
File transfer: reassigning a file (an eMER) to the correct applicant
This is the main process that we have been following:
Assigning an eMER to the correct applicant
Applicant merge
This is used for merging duplicate files. It is different from File Transfer
Merging duplicate applicant files
Incoming eMER lost after being accepted
Incoming eMER lost after being accepted.
ORACLE error when updating CAME profile
Solution for oracle error when updating CAME profile
CAMIS / eMER Region Change:
CAMIS / eMER Region Change - BSD - Civil Aviation - Confluence (atlassian.net)
Expand | |||||
---|---|---|---|---|---|
| |||||
The following script is used to fix an ongoing issue with the document naming scheme. The issue is that eMER adds the date of submission in the file name, but CAMIS doesn’t expect it. eMER does: CAMIS expects: Script to run:
|
Expand | ||
---|---|---|
| ||
User must be added into 2FA database before they are able to give eMER access to CAMEs To log in to eMER, the user must have a valid cell-phone number in their CAMIS profile in order to receive the 2FA SMS code.
6. If we can not find any error in above steps, and even if the eMer status is changed from Inactive to active and CAM still does not get the 2FA SMS code: Email to a CAMIS administrator to keep a copy of original number, modify that phone number in CAMIS to the different one (fake ones), with the “active” eMER status, click update, then put back original phone number, click update. CAMIS administrator then will need to generate a new activation code. CAM will sign in eMER using the new activation code and he/she would receive 2FA SMS codes after that. |
Expand | ||
---|---|---|
| ||
Note: The assignor is able to delete any tasks they created. Tasks are saved in |
Expand | |||||
---|---|---|---|---|---|
| |||||
Example: Open CAMIS, enter the file no, get to the specific MER record and “View eMER record”, the “Submit MER Confirmation” will show the Applicant Details' name is different from Applicant (on top of the page). On the same page, go to the “Documents” section, you must see the wronglastname-wrongfirstname--mer.html and wronglastname-wrongfirstname--mer.pdf. How this issue can happen: CAME (doctor) creates a new applicant on EMER application with the right name of applicant He enters medical data, however at Applicant Details section, he enters the wrong given name and wrong last name. He has to view, click the check box before click “Submit MER”. However, he might forget to review the names here After summitting MER, the file has been submitted to CAM (CAMIS client) and there is a wronglastname-wrongfirstname--mer.html which contains all medical data is saved in the UA018_document table with a document_nbr On CAMIS application, CAM is now opening the file, checking the “incoming eMER' and assigning the file to a specific CAM . At this point, I do not know yet that specific CAM has done something on the file (he might confirm it), then there is wronglastname-wrongfirstname--mer.pdf saved in the UA018_document table with the next document_nbr Database Notes We can find licence_nbr and medical_examination_id in UA006_medical_examination WE can find html and pdf file under UA018_document Here is the SQL we can use to check if the person has the right names in the medical files. These info will be shown on the file names This below SQL is from PK_EMER_MEDICAL_EXAMINATION.SP_get_mer_step6
Fix: Using database within CAMISP.WORLD,
|
Expand | ||
---|---|---|
| ||
The clients cannot modify eMer on Camis because submitted date of the eMER is before the medical examination date. This happens when CAM chooses the examination date in the future Fix: Find the medical_examination_id from the client’s information, on UA006_MEDICAL_EXAMINATION, change the medical_examination_dte is before or equal date_emer_submitted_dte |
Expand | ||||
---|---|---|---|---|
| ||||
Required info: The file no. that was incorrectly assigned and the correct file no., applicant id that the eMER should be assigned to.
Required info: The name of the applicant and stamp number of the examiner (or exam date). Within CAMISP.WORLD, in the table
Required info: The license number of the first applicant and of the second. Make sure to first check that both license numbers exist in CAMIS. If not, you will need to wait for it to get populated in DAPLS. The following script merges an applicant into another one (MERs, related activities, assessments, docs, etc.).
Create a related task and include the script you ran. Verify in the application if the changes were successful, you can search the correct file no. and look in the Tests & Docs. and MERs tabs to verify if the files are there. In CAMIS (prod): Enter the file number in the resulting form: |
Expand | ||
---|---|---|
| ||
On CAMIS, entering a file number, at Tombstone tab, click on “Add/Update Indicators”, if there are missing indicators: Check YA003_APPLICANT of that applicant, at date_deleted_dte to see whether the field is empty or not. If that field can be empty, then the missing indicators will appear |
Expand | |||||
---|---|---|---|---|---|
| |||||
When we have a task to delete address associated with stamp number (see bug # 244024 Delete address associated with stamp number) Within CAMISP.WORLD, in the table In the table
|
Expand | ||
---|---|---|
| ||
related DevOps Task: 201977 eMER found in applicant's Test & Docs tab not in MERs Tab If an eMER is not listed under “Incoming eMERs” in CAMIS:
2. If the eMER was deleted by the CAME (or business client) follow-up with the requestor to confirm if the record should be deleted. If the requestor confirms the record should be undeleted, update the DATE_DELETED_DTE to NULL.
|
CAMIS Report Generator
This program needs to be run weekly on Monday until the changes to CAMIS/eMER have been finalized.
CAMIS Report Generator: performing the weekly auto-accept
TFS Testing Plans, Suites and Test Cases imported:
...