Uploaded image for project: 'FHIR Specification Feedback'
  1. FHIR Specification Feedback
  2. FHIR-28222

Naming rules for extended / custom operations

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive with Modification
    • Icon: High High
    • FHIR Core (FHIR)
    • R4
    • FHIR Infrastructure
    • OperationDefinition
    • (NA)
    • Hide
      Show
      Link to https://confluence.hl7.org/display/FHIR/Guide+to+Designing+Resources#GuidetoDesigningResources-NamingRules&Guidelines  from OperationDefinition page (specifically from "code" element or others where rules apply) Do not implement invariants at this point
    • 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

      Attachments

        Activity

          People

            GrahameGrieve Grahame Grieve
            jkiddo Jens Villadsen
            Grahame Grieve, Lloyd McKenzie
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: