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

I would use another term here

    XMLWordPrintableJSON

Details

    • Icon: Change Request Change Request
    • Resolution: Not Persuasive
    • Icon: Highest Highest
    • Clinical Quality Language (FHIR)
    • 1.4
    • Clinical Decision Support
    • Introduction
    • 3.3. Physical Perspective
    • Hide

      Given the domain of data modeling and query languages, and the intended layering, and the fact that this is a central organizing principle for the specification, prefer to keep the name physical, and note that the term "machine perspective" is explicitly used in defining the Physical layer when it is introduced.

      Show
      Given the domain of data modeling and query languages, and the intended layering, and the fact that this is a central organizing principle for the specification, prefer to keep the name physical, and note that the term "machine perspective" is explicitly used in defining the Physical layer when it is introduced.
    • Chris Moesel/Phillip Warner: 14-0-0

    Description

      "Physical" is potentially not the right term as then I think of atoms and physical matter and encoding bits using magnetic fields or other physical means as electric currents or punch cards.

      I would rather use Machine Perspective as can be conveyed by the fact that the low-level encoding that can directly be understood by the machine is, for instance, the "binary code", which is also often referred to as "machine code".

      Even then what you imply is probably a level higher as you state: "specifically, with how the canonical representation of expression logic is shared between producers and consumers". The latter makes me thing of something like: "Realization" or "Communication" Perspective.

      Existing Wording:

      3.3. Physical Perspective

      Proposed Wording:

      3.3 Realization Perspective

      Attachments

        Activity

          People

            Unassigned Unassigned
            ivan_zapreev Ivan Zapreev (Inactive)
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: