Evaluate moving ITI-30 and ITI-31 to required actor groupings

Currently, ITI-30 (Patient Identity Management) and ITI-31 (Patient Encounter Management) are listed directly as SMRT transactions in Table XX.1-1. This creates confusion, especially regarding the optional reverse flow (TMS acting as initiator / ROIS as responder).

In standard IHE methodology, if a profile reuses existing transactions, those should generally be handled via Actor Groupings with the profile that originally defines them (in this case, ITI PAM). We need to evaluate whether we can make this shift.

Evaluation Steps:

1. Assess Requirements: Review our current specifications for demographics and encounters. We must confirm whether SMRT introduces any relaxed requirements compared to standard PAM. (Note: Additional/tighter constraints can be handled via grouping text, but relaxed constraints cannot).
2. If valid (no relaxed requirements):
   • Remove ITI-30/ITI-31 from the SMRT Actors and Transactions Table (Table XX.1-1).
   • Remove their corresponding transaction descriptions from the "Transaction Descriptions" section.
   • Update the Required Actor Groupings Table (Table XX.3-1) to mandate that ROIS groups with PAM Patient Demographics/Encounter Supplier, and TMS groups with Patient Demographics/Encounter Consumer.
   • Document the reverse flow (TMS to ROIS) as an optional grouping under Cross-Profile Considerations (XX.6).
3. If invalid (SMRT relaxes constraints OR fundamental changes exist):
   • Keep ITI-30/ITI-31 as profiled transactions within SMRT.
   • Explicitly document how the reverse flow is managed so it is no longer confusing for implementers.

Review the current demographics and encounter requirements, then compare them with ITI PAM to determine whether SMRT relaxes any constraints. If grouping is valid, update Table XX.1-1, the Transaction Descriptions section, Table XX.3-1, and Cross-Profile Considerations (XX.6); otherwise retain the transactions and clarify the reverse flow. Done means the chosen approach and its implementer guidance are explicit.