Remove tag token
article thumbnail

Our passwords, ourselves -- the nightmare of authentication

Aging in Place Technology Watch

a) Find your phone, b) accept the text message, c) copy the ‘we will never share your information with others’ privacy token into the appropriate location on the screen. Older adults (forget that insulting ‘grandma’ in the title) do not love 2-factor authentication with security tokens either (too small). Feeling safe and protected.

111
111
article thumbnail

Break-Glass

Healthcare Exchange Standards

But would require that there be some yet-to-be-defined code to indicate that Break-Glass may be useful The FHIR Bundle that is returned might have a Bundle.meta.security tag that indicates that some data were redacted ( REDACTED ). This tag would not be included for those users not authorized to declare Break-Glass.

FHIR 98
Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Teaching an AI/ML/LLM should be a distinct PurposeOfUse

Healthcare Exchange Standards

this would require tagging each data resource. this would require tagging each data resource. can be used in a Consent, where allowed, to allow an individual patient to express rules specific to that purposeOfUse. can be used in a Consent, where allowed, to allow an individual patient to express rules specific to that purposeOfUse.

52
article thumbnail

Did you miss one? Five Aging and Health Tech blog posts March 2023

Aging in Place Technology Watch

a) Find your phone, b) accept the text message, c) copy the ‘we will never share your information with others’ privacy token into the appropriate location on the screen. Signing on to my bank account on a computer – there is that two-factor authentication (2FA) thing again. Feeling safe and protected.

article thumbnail

FHIR Security initiatives

Healthcare Exchange Standards

This specifies three levels: Bearer token, JWT token, and SAML encapsulated. This workgroup maintains security-tagging within the FHIR Resource header. So that each resource can be tagged with security (privacy) relevant tags that can be used in the Access Control decision, and can carry Obligations to a recipient.

FHIR 40
article thumbnail

FHIR Security and Privacy - tutorial outline

Healthcare Exchange Standards

These tags are used in an "Attribute Based Access Control" scheme. That is to say that an Access Control engine will use these meta tags to inform the decision that it makes; and can place tags into meta to inform any downstream Access Control engine (decision or enforcement).

FHIR 40
article thumbnail

Break-Glass on FHIR solution

Healthcare Exchange Standards

Using Security-Labels The security-labels include the full vocabulary from the Healthcare Privacy and Security Classification System (HCS), so there are security tags that can be used to indicate for each Resource instance if it is "Normal" or "Restricted". This solution does require well managed tags on all data.

FHIR 40