-
Type:
Change Request
-
Resolution: Persuasive with Modification
-
Priority:
Medium
-
FHIR Core (FHIR)
-
DSTU1 [deprecated]
-
FHIR Infrastructure
-
Terminology Service
-
1.23.6.2
-
-
Grahame Grieve / Eric Haas: 4-0-0
-
Clarification
-
Non-substantive
-
DSTU1 [deprecated]
Existing Wording: Note to reviewers/implementers: can we? it would increase interoperability if we could bind to a particular approach. If we said, for the operations, SSL+server certs mandatory, use client certificates if you want to authenticate the clients, and to use Smart on FHIR for editing value sets and concept maps, is there any problems with that?
Comment:
Response: Happy with mandatory SSL/TLS+Server Certificate, and optional client certificate authentication. Not sure whether editing Value Set content with SMART-on-FHIR is necessary to increase interoperability.
- is voted on by
-
BALLOT-848 Affirmative - Andy Bond : 2015-May-FHIR R1
- Closed