OwS Object Type: ''Domain

OwS allows to place terminologies, ontologies and other objects into the context of a domain. A domain defines the scope of its contained objects and can be used as a tool for grouping OwS defined objects.

Defined Properties

Property Name	RWDS	Type	Subtype	Card.	Definition
_name	RD	string		1..1	OwS managed property: OwS-internal name of the object. Set when the object is initially defined (see define statement). Shall be used for referencing this object from othe OwS objects.
_type	RD	string		1..1	OwS managed property: "Domain"
display	RW	string		0..1	Display name of the domian. If no display name is set, the OwS-internal name will be used as the display name.
version	RW	string		0..1	allows for maintaining the change history of a domian definition
status	RW	code		0..1	draft | active | retired | unknown (code from FHIR PublicationStatus value set)
description	RW	collection	string	0..1	not yet implemented
groupname	RW	string		0..1	CTS2-LE specific: Folder within the CTS2-LE terminology browser where Codesystem objects linked with this domain shall be placed.
hierarchyMeaning	RW	code		0..1	(grouped-by | is-a | part-of | classified-with) from FHIR CodeSystemHierarchyMeaning value set.
_temp	RW	string		0..1	for your own disposition

RWDS = Read Access - Write Access - Default Value if not explicitly set - Special Treatment

Nesting Domains and References to Domains

Domain objects can be nested: every domain may hold multiple [0..*] subdomains. When nesting domains, a subdomain inherits the version and groupname property from its superdomain. Both properties may be overwritten by the subdomian.
All domains - including subdomains - shall have unique names. When referencing a domain or subdomain only the name of the domain needs to be provided.

define Domain ADT {
  define Domain Admission { }
  define Domain Discharge { }
  define Domain Transfer { }
} 

define Codesystem TransferReason {
  ...
  set .context = Transfer
}