The Endpoint.status element has a required binding to the EndpointStatus value set but based on the available concepts I think we have conflated two separate issues. The "test" code isn't really a status. Instead it represents what most implementers would consider an environment. Most real organizations maintain multiple separate environments for development, test, staging, and production.

I propose the following changes. In the EndpointStatus value set remove the "test" concept. Add a new Endpoint.environment element with cardinality 0..1 and extensible binding to a new EndpointEnvironment value set. The concept codes in that new value set should be "development", "test", "staging", "production".