We will revise the definition of two of the entryMode codes: sequential: "Questions are displayed one at a time. Previous questions and submitted answers cannot be viewed or edited." to "Top-level items are displayed one at a time and items within groups are displayed one at a time, with certain exceptions.  If an item is of type 'page', then all items within the page are displayed and can be edited.  If a question has child questions, the parent question (and answers) are visible while descendant questions are being edited.  Once a user has progressed to view subsequent items, they can no longer return to edit or view prior items (though they might be able to see all answers once the questionnaire response has been marked 'completed' and is no longer editable).  These questionnaire responses cannot be 'amended'." prior-edit: "Questions are only displayed once prior questions have been answered (or if optional, skipped). Previously answered questions are available for viewing and potentially editing" to "This behaves similar to sequential from a 'display' perspective.  I.e. items are generally only displayed one at a time.  However, with his mode, it is possible to navigate to prior questions and change answers.  Amending completed forms is possible." Will add usage notes to the 'entryMode' extension: "When the entryMode is one that will prohibit the user from going back to edit preceding questions, the form filler must ensure that the answer meets all validation constraints (cardinality, length, etc.) prior to allowing the user to progress to subsequent items.  However, when the entryMode allows editing prior items, then form fillers SHOULD allow a user to move on and answer subsequent items, with the recognition that they'll eventually have to go back to make corrections before the QuestionnaireResponse can transition to a status of 'complete'. Note: if the only objective is to ensure that certain future questions/groups aren't turned on until/unless specific previous items are satisfactorily completed, this should be accomplished using [enableWhen] or [enableWhenExpression] ."