-
Type:
Change Request
-
Resolution: Not Persuasive with Modification
-
Priority:
Medium
-
FHIR Core (FHIR)
-
STU3
-
FHIR Infrastructure
-
Normative
-
Conformance Rules
Extensibility
Profiling -
-
Ewout Kramer / Yunwei Wang: 9-0-0
-
Clarification
-
Non-substantive
-
STU3
IHE has used the word Profiling for decades. This word has been used for similar level of use-case by WS-I, OASIS, W3C, and IETF. In all cases the use of the word Profiling is broader than used in FHIR specification. In those cases the use of the word is more closely aligned with HL7 "Implementation Guide". This is known to the healthcare interop community, they understand this.
The FHIR use of profiling as a sub class of StructureDefinition is sewing confusion. I understand the technical reasons for using the word profile for what it is being used for regarding StructureDefinition. This is however not complete enough. This lesser meaning is technically correct, I am not arguing on technical means. I am arguing on human understanding, and ultimately specification understanding.
Arguments that FHIR use of 'profiling' is too baked into the specificaiton is unacceptable since it is not in FHIR in any normative way. Where it is normatively baked into IHE and other organizations.
Thus please change from "profile" and "profiling" to "constraint", and "constraining". This is far more close to what you are including in the definition.
Or use some other word or phrase. Continuing to sew confusion in the healthcare space over this simple word is unacceptable. There is no benefit gained by this confusion.
- is duplicated by
-
FHIR-13470 Be specific with the use of the word Profile
-
- Duplicate
-
- is voted on by
-
BALLOT-4761 Negative - John Moehrke : 2018-May-FHIR R4 INFRASRUCTURE R1
- Balloted