1	Naming, Trader, PIDS, LQS Interoperation
The Naming, Trader, PIDS and LQS Standards are considered building blocks and as such are of great value to COAS, hence, the following information is supplied in order to provide a level of understanding where each may play a role. 

1.1	Naming/Trader
It is anticipated that the CORBA Naming and/or Trader Services may be used for acquiring pertinent information about the capabilities of a COAS compliant service. For these purposes the AccessComponent Interface has been defined. For the Naming Service the naming_service attribute will define the Naming Context.

For the "kind" field in CosNaming:NameComponent the following will be used:
•	 ‘Query COAS’ - A COAS component that meets the conformance class of the same name.
•	‘Browse COAS’ - A COAS component that meets the conformance class of the same name.
•	‘ConstraintLanguage COAS’ - A COAS component that meets the conformance class of the same name.
•	‘Asynchronous COAS’ - A COAS component that meets the conformance class of the same name.
•	‘Supplier COAS’ - A COAS component that meets the conformance class of the same name.
•	‘Consumer COAS’ - A COAS component that meets the conformance class of the same name.
•	‘Federated COAS’ - A COAS component that meets the conformance class of the same name.

The following definitions are Service Types defined for COAS components for use by the Trader Service.
Service AccessComponent
{
Interface AccessComponent;
Mandatory readonly property StringSeq components_implemented;
Readonly attribute StringSeq pid_service;
Readonly attribute StringSeq terminology_service;
Readonly attribute StringSeq trader_service;
Readonly attribute StringSeq naming_service;
Readonly property String component_name;
Readonly property String component_version;
Readonly property StringSeq supported_codes;
Readonly property StringSeq supported_qualifiers;
Readonly property StringSeq default_policies;
Readonly property StringSeq supported_policies;
};
1.2	PIDS
The COAS specification has introduced the idea of an ObservedSubject, but has made the distinction that it lies outside the scope of this specification in order to allow this specification to be used in varying medical architectures. However, because an ObservedSubject can be a person(patient) we recognized the value in utilizing the PIDS specification in order to identify a person in an enterprise. We have introduced the idea of a PIDS domain in the AccessComponent attribute called pids_domain_name as well as an attribute called pid_service to denote a PIDS service.
1.3	LQS
The COAS specification utilizes many of the concepts from the Lexicon Query Service (LQS) specification in order to provide a more dynamic and extensible specification. The COAS specification does not however mandate the use of any particular LQS but recognizes that it provides all the necessary interfaces for a client or server to attain information from coding schemes to assist in semantic interoperability at a coded level. We have also introduced the idea of an LQS rterminology service via the AccessComponent interface attribute callled terminology_service thereby providing a link to terminology services.