| 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 |
...
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
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.
Account access issues:
CAME Accounts:
...
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
...