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

Organization does not technically have a "status" element. It has an "active" element.

    XMLWordPrintableJSON

Details

    • Change Request
    • Status: Published (View Workflow)
    • Medium
    • Resolution: Persuasive with Modification
    • US Core (FHIR)
    • 4.0.0
    • Cross-Group Projects
    • Profiles and Extensions
    • Hide

      Background:

      The text the commenter is referring to:

      Mandatory and Must Support Data Elements

      The following data-elements must always be present (Mandatory definition]) or must be supported if the data is present in the sending system (Must Support definition). They are presented below in a simple human-readable explanation. Profile specific guidance and examples are provided as well. The Formal Profile Definition below provides the formal summary, definitions, and terminology requirements.

      Each Organization must have:

      1. A status of the organization
      2. ...

      The Documentation attempts to provide a human readable description of the requirement in contrast to the formal definitions. The friendlier term "status" was used because it is a status element that can indicate that a record should not be treated as valid.

      Reasoning:

      We don't believe this description needs to align with the more formal organization element name, however we will clarify it parentheticially.

      Proposed Changes:

      Will update to:

      1. A status of the organization (i.e. active element populated)

       

       

      Show
      Background: The text the commenter is referring to: Mandatory and Must Support Data Elements The following data-elements must always be present ( Mandatory  definition]) or must be supported if the data is present in the sending system ( Must Support  definition). They are presented below in a simple human-readable explanation. Profile specific guidance and examples are provided as well. The  Formal Profile Definition  below provides the formal summary, definitions, and terminology requirements. Each Organization must have: A status of the organization ... The Documentation attempts to provide a human readable description of the requirement in contrast to the formal definitions. The friendlier term "status" was used because it is a status element that can indicate that a record should not be treated as valid. Reasoning: We don't believe this description needs to align with the more formal organization element name, however we will clarify it parentheticially. Proposed Changes: Will update to: 1. A status of the organization (i.e. active element populated)    
    • Floyd Eisenberg/Eric Haas: 12-0-2
    • Clarification
    • Non-substantive

    Description

      Currently, the description of what is required for Organization includes:

      i.e. Organization must have a status.

      There is no "status" field in the structure. However, there is an "active" field which does identify the status of the organization as active or inactive

      We should rephrase the "status" requirement for what organization must support. 

      Attachments

        Activity

          People

            Unassigned Unassigned
            hbader Hayden Bader
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: