273 hl7 2024 jan resolve or remove tbd statements from text (#349)

* Resolution of issue #273 as discussed

* Added CHANGELOG entry for issue #273

CHANGELOG.md

@@ -26,6 +26,7 @@ Each section shall contain a list of action items of the following format: `<bri
 - Addressed three JIRA tickets listed in issue ([#275](https://github.com/IHE/DEV.SDPi/issues/275))
 - Corrected some entries in "1:B.1 Referenced Standards" for consistency ([#267](https://github.com/IHE/DEV.SDPi/issues/267))
 - Commented out concept sections 1:10.4.1.3 thru 1:10.4.1.10 and minimized referencing to years for improving readability ([#268](https://github.com/IHE/DEV.SDPi/issues/268))
+- Removed TBD statements from Table A-1 ([#273](https://github.com/IHE/DEV.SDPi/issues/273))
 
 
 ## [1.4.1] - 2024-10-04

asciidoc/volume0/tf0-ch-a-actors.adoc

@@ -112,18 +112,14 @@ The table below lists _existing_ actors that are utilized in this specification.
 |===
 |Existing Actor Name |Definition
 
-|[[actor_alert_aggregator,Alert Aggregator]] Alert Aggregator  +
-*_(TBD) -- If the ACM Gateway uses this_*
-| This actor receives alerts from the Alert Reporter and collects status events related to the dissemination of the alert.
-
 |[[actor_alert_consumer,Alert Consumer]] Alert Consumer
 | The Alert Consumer (ACON) receives the alert from the Alert Reporter (AR) and uses the alert information strictly as a consumer of the alert being raised.  There is no implementation requirement for how the ACON ultimately uses the alert information.
 
 |[[actor_alert_manager,Alert Manager]] Alert Manager
 | The Alert Manager (AM) receives the alerts from the Alert Reporter (AR), potentially analyzes the alert, and dispatches the alert to the Alert Communicator (AC), and optionally, provides the alert to the Alert Archiver (AA) or Alert Consumer (ACON) upon subscription.
 
 |[[actor_alert_reporter,Alert Reporter]] Alert Reporter
-| This actor originates the alert (an alarm, either physiological or technical, or an advisory). May also query the Alert Aggregator for the status of the alert.
+| This actor originates the alert (an alarm, either physiological or technical, or an advisory).
 
 |[[actor_device_observation_consumer,Device Observation Consumer]] Device Observation Consumer
 | The actor responsible for receiving PCD data from the Device Observation Reporter, the Device Observation Filter, or both.
@@ -132,8 +128,8 @@ The table below lists _existing_ actors that are utilized in this specification.
 | The Device Observation Reporter (DOR) receives data from PCDs, including those based on proprietary formats, and maps the received data to transactions providing consistent syntax and semantics.
 
 
-| Time Client +
-*_(TBD -- Do dependent profile actors like CT TC get included in this table?)_*
+| Time Client
+
 | Establishes time synchronization with one or more Time Servers using the NTP protocol and either the NTP or SNTP algorithms.  Maintains the local computer system clock synchronization with UTC based on synchronization with the Time Servers.
 
 |===