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

Add formal text

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Low Low
    • Shorthand (FHIR)
    • 0.12.0 [deprecated]
    • FHIR Infrastructure
    • Language Reference
    • 1
    • Hide

      Following other similar specs, even some that are normative (such as CQL), I didn't see formal introduction of keywords. FSH should follow whatever is typical in HL7 standards.

      Show
      Following other similar specs, even some that are normative (such as CQL), I didn't see formal introduction of keywords. FSH should follow whatever is typical in HL7 standards.
    • Kramer/Rhodes: 14-0-0

    Description

      In order to clearly indicate what part of the specification is required, adviced and optional. Formal text should be included including a refernce to the related specification: Add section that refers to ISO… for definition of the mandatory language (SHALL, SHOULD, …)
      The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this specification are to be interpreted as described in RFC2119.

      Attachments

        Activity

          People

            Unassigned Unassigned
            bvdh Bas van den Heuvel
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: