-
Type:
Change Request
-
Resolution: Persuasive with Modification
-
Priority:
Medium
-
US Da Vinci HRex (FHIR)
-
current
-
Clinical Interoperability Council
-
Security and Privacy
-
-
Bob Dieterle / Richard Esmond : 9-0-1
-
Clarification
-
Non-substantive
update this section to:
FHIR Clinical Safety
Clinical Safety is a key concern with regard to this specification and the many and implementations that reference it. Implementers SHOULD follow the FHIR Implementer’s Safety guidance as defined in the FHIR specification where applicable and not superseded by this Section or specific IG requirements. The FHIR Implementer’s Safety specification is a check list to help implementers be sure that they have considered all the parts of FHIR that impact their system design regarding safety.
FHIR Security and Implementation Guidance
FHIR is not a security protocol, nor does it define any security related functionality. However, FHIR does define exchange protocols and content models that need to be used with various security protocols defined elsewhere. All FHIR Implementation Guides SHOULD follow the FHIR Security guidance as defined in the FHIR specification where applicable and not superseded by this Section or specific IG requirements. The FHIR Security specification provides guidance related to communication security, authentication, authorization/access control, audit, digital signatures, attachments, labels, narrative, and input validation. The FHIR security specification is available here.
- relates to
-
FHIR-30490 clinician burden reduction
-
- Resolved - change required
-
-
FHIR-30490 clinician burden reduction
-
- Resolved - change required
-
- mentioned in
-
Page Loading...