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

Document conventions used in the IG

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Persuasive
    • Icon: Medium Medium
    • Canonical Resource Management Infrastructure (FHIR)
    • current
    • Clinical Decision Support
    • Home
    • Hide

      Agreed, document conventions as suggested

      Show
      Agreed, document conventions as suggested
    • Floyd Eisenberg/Greg White: 13-0-0
    • Clarification
    • Non-substantive

    Description

      Naming conventions for artifacts throughout the IG:

      FIlenames: <ResourceType>-<id>.<format>

      Canonical Resources (Profiles, CodeSystems, ValueSets, OperationDefinitions, CapabilityStatements): url should be <base canonical>/StructureDefinition/crmi-<resource-id>

      name should be CRMI<pascal-cased-profile-id>

      title should be CRMI <title-cased-profile-id>

      Extensions: These will be defined in the extensions pack so will follow the convention there

      OperationDefinitions: Canonical resources conventions + code should be $<ig-code>.<operation-code> e.g. $crmi.release

      Add a section in this IG documenting these conventions and suggesting they be adopted for other IGs (we might want to discuss this with FHIR-I)

      Attachments

        Activity

          People

            Unassigned Unassigned
            bryn.rhodes Bryn Rhodes
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: