...
- Next, get an accurate picture of your current Noah setup:
- How many computers with Noah?
- What version of Noah is on the machines?
- Are you combining databases from standalone machines or multiple offices?
- How many unique users will be accessing Noah?
- Do they have user accounts?
- Have passwords been enabled in Noah?
- Do the users know their passwords?
- Are they using complex passwords?
- Next, think about your Noah user accounts and passwords
- For Phase One of the Noah as a Service testing HIMSA will be providing you with test Noah User Accounts and Passwords to log into the remote Noah Server. You will continue to user your existing accounts when logging into your own local Noah.
- For Phase Two, your patient database will be moved to your remote Noah Server hosted by HIMSA and HIMSA requires that login security is enabled and 'Enforce strong user passwords' is selected. See details in the box below and a screen shot of where to locate these security settings in the Noah Console.
| Insert excerpt | ||||
|---|---|---|---|---|
|
...
You will find these settings in the Noah Console at Security Administration, Login.
Once you have reviewed your current Noah configuration and updated all computers to Noah 4.10, the next step is to create an account on the Noah as a Service support portal.