| Element Name | Location |
|---|
| Parent |
|---|
Element(s)| Elements | AdminData |
|---|
| Element XPath(s) | /ODM/AdminData/Location |
|---|
| Element Textual Value | None |
|---|
Usage | Conditional. There must be an ItemDef element for each unique ItemOID attribute value in the study. |
| Attributes | OID, Name, Role, OrganizationOID |
|---|
,(Description?, MetaDataVersionRef+, Address*, Telecom*, Query*), OrganizationRef*...
| Attribute | Schema Datatype or EnumerationDefinition | | OID | oid | Required | Unique identifier | Must be unique for a Study. |
| Name | name | Required | Human readable identifier. | Must be unique within the set of Location defintions for the Study. |
Role | text | Optional | Specifies the role of this location in the study. | Contained in:
...
- Business Rule(s):
- When the ODM FileType attribute is set to "Transactional", a Location element must be provided for each LocationRef/@LocationOID value in AuditRecord or Signature child elements in the ClinicalData.
- Other Information:
- The Location may be referenced in an AuditRecord or Signature in the ClinicalData.
- The address of the location can be
|
...
- used to ascertain the local time associated with a DateTimeStamp.
|