CAMIS - SIMAC
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:
• A secure Internet-based application;
• Online access to current and previous medical history of applicants;
• Electronic submission of medical reports of licensed aviation personnel; and
• Online assessments of the reports and secure storage of medical documentation and
assessment results.
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 |
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
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
application. Version 3.0 integrates CAMIS with the Distributed Air Personnel Licensing System
(DAPLS) ensuring synchronization of tombstone, address, and medical assessment information;
including medical license category and any medical licensing restrictions pertaining to the
issuance of the license (e.g. glasses must be worn).
The Civil Aviation Medical Information System (CAMIS) is a web based application used by the Civil Aviation Medicine (CAM) Group to track and assess medical reports of licensed aviation personnel.
CAMIS is tightly linked with eMER - eREM (share a database).
Entrust True Pass is used to authenticate users' MyKey before they are able to access the website.
The pilot records are maintained in DAPLS. A certified pilot needs to be certified medically. DAPLS updates license numbers to CAMIS but I think CAMIS will update licenses' medical information to DAPLS (we will review it later).
Good To Know
The first version of CAMIS was put in production in 2004 in Java and updated in 2010 as a .net wersion.
CAM: Civil Aviation Medicine - the CAMIS Client, CAM will process the applications from eMERS in the internal CAMIS application
CAME: Doctors working at Apple Tree doing medicals on behalf of TC. Doctors make applications on behalf of the pilots. They will do these through eMER
Medical Examination Date has to be before or equal submitted eMER date, otherwise CAM can not process the record. Both of the dates are inside the table UA006_MEDICAL_EXAMINATION. Errors are sometime happening because eMER allows to submit to CAMIS the future examination date!!!
Files for testing attachment types:
see Files for testing attachment types
Deploying CAMIS to development, acceptance and production: |
---|
How-To and Fixes
Suggested credential for any fix:
Development: CAMIS_DATA_ADMIN@CAMISD
Acceptance: CAMIS_DATA_ADMIN@CAMISA
Production: CAMIS_DATA_ADMIN@CAMISP
Backing up Production Data:
Production data should be backed up before it is changed. This document provides the steps for backing up data using TOAD.
Backing up Production database data
Oracle errors: localhost and deployments (dev, acc, prod)
How to get CAMIS Working When it Runs with Oracle.DataAccess Error
Applies to:
localhost
publishing packages for development, acceptance and production
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
https://tcmarin.atlassian.net/wiki/spaces/CA/pages/2851045383
CAMIS / eMER Region Change:
CAMIS / eMER Region Change - BSD - Civil Aviation - Confluence (atlassian.net)
TFS Testing Plans, Suites and Test Cases imported: