Why do you need an iTag MedCard?

For Patient Medical Records Security

iTag Cybersecurity starts when the

Hospital Computer is first turned on.

MedCard Authentication

needs to build a

“Circle of Trust”

that proves the Patient, Doctor,

Nurse(Admitting or Emergency),

Employee,

Caretaker/Nursing Home

is who they say they are

The Secure MedCard

is what it says it is,

the Hospital computer is who it says it is,

and the server(MedBase -> Epic Systems)

is what it is.

Here is how the MedCard Logon solves this problem.

Patient to MedCard

3 Factor Authentication 

(Known in the Security world as 3FA)

1.  Something you have  – The MedCard

2.  Something you Know – Your Pin

(The PIN only unlocks access to the MedCard Security Chip)

3.  Something you Are – Biometrics of Your Fingerprints and Photo

Next

The Hospital Computer needs to Authenticate to the Hospital Server – 

Up the 3FA!

1.  Something the Computer Has – The MedCard

2. Something the Computer Knows – the MedCard encryption keys (MedKeys)

3. Something the Computer Is – Computer unique identifier (MedBytes)


Great, but let’s take this up another level:

Server to MedCard and MedCard to Server Challenge-Response.

Number 1:

The server generates a unique code (MedBytes Byte 1) based on the information it knows about a specific MedCard.

b. The MedCard also generates a unique code (MedBytes Byte 2) that it knows about the server.

c. If these two numbers match, then the MedCard knows it’s connected to the correct server, and the server knows it is connected to the right MedCard.

d. Challenge-Response eliminates the risk of a cloned MedCard.

Server to MedCard and MedCard to Server Challenge-Response

Number 2

1. Because the user authenticated to the MedCard with MFA earlier, the server now has a very high level of trust that the user is who they say they are.


Almost Finished...

1. After these verifications, the computer can access and decrypt the Windows Login Username and Password store in “Active Directory” or other LDAP (Lightweight Directory Access Protocol).

2. Autofill the Windows logon page without the user knowing and seeing any of this information.

                                  Finally,

3. We can also add in a Status Level code that software programs can look for to determine what information a user is allowed and not allowed to access from a central database.

This ability does require that the database base support this security.


Patient > MedCard > Computer > Server > MedCard > Computer > Patient
=
The Circle of Trust.

iTag Medical Products

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Ut elit tellus, luctus nec ullamcorper mattis, pulvinar dapibus leo.

Progress Bars

Pricing Tables

Flip Boxes

Service Boxes

Partners

Accordions & Tabs

Counters

Countries Worldwide

To succeed, every software solution must be deeply integrated into the existing tech environment..

Happy Customers

To succeed, every software solution must be deeply integrated into the existing tech environment..

Testimonials

Message Boxes