Details
-
Change Request
-
Resolution: Persuasive with Modification
-
High
-
FHIR Core (FHIR)
-
R4
-
FHIR Infrastructure
-
OperationDefinition
-
(NA)
-
-
Grahame Grieve / Rick Geimer: 9-0-1
-
Clarification
-
Non-substantive
-
R5
Description
Apparently, there are rules for naming an operation, stated at https://confluence.hl7.org/pages/viewpage.action?pageId=35718826#GuidetoDesigningResources-NamingRules&Guidelines
These naming rules for FHIR operations are not mentioned in the specification itself - neither is the casing of the name eg:
- camelCase
- PascalCase
- snake_case
or
- kebab-case
I suggest that the OperationDefinition should have an invariant flagging the violation of the naming rules as warnings if OperationDefinition.code does not follow these rules.
See also https://chat.fhir.org/#narrow/stream/179166-implementers/topic/custom.20operation.20naming