Remove tag argonaut-project
article thumbnail

FHIR Security initiatives

Healthcare Exchange Standards

It has taken input from various Healthcare initiatives including SMART, and Argonaut. I understand that this is further being developed now under Argonaut Project. This workgroup maintains security-tagging within the FHIR Resource header. There are some key people involved from healthcare, more people are always welcome.

FHIR 40
article thumbnail

Actual Consent is more important than more standards for Consent

Healthcare Exchange Standards

The application of security vocabulary as request context (purposeOfUse), response obligations (do not re-disclose), and data tags (confidential and sensitive). But if security (or CBCP) did the project, no one outside of our workgroups would care. Because Patient Empowerment workgroup is deep in two other projects at this time.

article thumbnail

Privacy and Security Considerations for the use of Open APIs for Patient Directed Exchange.

Healthcare Exchange Standards

Such as the many FHIR open source projects ; Standard Interpretation of Regulation -- like HHS/ONC has done with for example the use of email with patients ; and Laws and Regulations -- we all hope for as few regulations as possible, but sometimes they are needed. Data-Tagging? I do expect there is still some standards needed.

FHIR 49