diff --git a/cdisc_rules_engine/enums/default_file_paths.py b/cdisc_rules_engine/enums/default_file_paths.py index 053698870..787263078 100644 --- a/cdisc_rules_engine/enums/default_file_paths.py +++ b/cdisc_rules_engine/enums/default_file_paths.py @@ -15,3 +15,10 @@ class DefaultFilePaths(BaseEnum): CODELIST_TERM_MAP_CACHE_FILE = "codelist_term_maps.pkl" CUSTOM_RULES_CACHE_FILE = "custom_rules.pkl" CUSTOM_RULES_DICTIONARY = "custom_rules_dictionary.pkl" + LOCAL_XSD_FILE_DIR = join("resources", "schema", "xml") + LOCAL_XSD_FILE_MAP = { + "http://www.cdisc.org/ns/usdm/xhtml/v1.0": join( + "cdisc-usdm-xhtml-1.0", "usdm-xhtml-1.0.xsd" + ), + "http://www.w3.org/1999/xhtml": join("xhtml-1.1", "xhtml11.xsd"), + } diff --git a/cdisc_rules_engine/exceptions/custom_exceptions.py b/cdisc_rules_engine/exceptions/custom_exceptions.py index ccb88c236..45c6ea06c 100644 --- a/cdisc_rules_engine/exceptions/custom_exceptions.py +++ b/cdisc_rules_engine/exceptions/custom_exceptions.py @@ -78,3 +78,13 @@ class UnsupportedDictionaryType(EngineError): class FailedSchemaValidation(EngineError): description = "Error Occured in Schema Validation" + + +class SchemaNotFoundError(EngineError): + code = 404 + description = "XSD file could not be found" + + +class InvalidSchemaProvidedError(EngineError): + code = 400 + description = "Failed to parse XMLSchema" diff --git a/cdisc_rules_engine/models/operation_params.py b/cdisc_rules_engine/models/operation_params.py index c5d956261..8f61177a2 100644 --- a/cdisc_rules_engine/models/operation_params.py +++ b/cdisc_rules_engine/models/operation_params.py @@ -57,3 +57,4 @@ class OperationParams: original_target: str = None returntype: str = None target: str = None + namespace: str = None diff --git a/cdisc_rules_engine/operations/base_operation.py b/cdisc_rules_engine/operations/base_operation.py index 625c8a145..3ac0e1205 100644 --- a/cdisc_rules_engine/operations/base_operation.py +++ b/cdisc_rules_engine/operations/base_operation.py @@ -37,6 +37,8 @@ InvalidDictionaryVariable, UnsupportedDictionaryType, FailedSchemaValidation, + SchemaNotFoundError, + InvalidSchemaProvidedError, ) @@ -85,6 +87,8 @@ def execute(self) -> DatasetInterface: InvalidDictionaryVariable, UnsupportedDictionaryType, FailedSchemaValidation, + SchemaNotFoundError, + InvalidSchemaProvidedError, ) as e: logger.debug(f"error in operation {self.params.operation_name}: {str(e)}") raise diff --git a/cdisc_rules_engine/operations/get_xhtml_errors.py b/cdisc_rules_engine/operations/get_xhtml_errors.py new file mode 100644 index 000000000..b56ddeee8 --- /dev/null +++ b/cdisc_rules_engine/operations/get_xhtml_errors.py @@ -0,0 +1,169 @@ +import os +from lxml import etree +import re + +from cdisc_rules_engine.exceptions.custom_exceptions import ( + SchemaNotFoundError, + InvalidSchemaProvidedError, +) +from cdisc_rules_engine.operations.base_operation import BaseOperation +from cdisc_rules_engine.enums.default_file_paths import DefaultFilePaths + + +class GetXhtmlErrors(BaseOperation): + """Validate XHTML fragments in the target column. + + Steps: + 1. Retrieve local XSD based on self.params.namespace + 2. Make sure the column is a valid XML -> on failure generate a list of XML validation errors + 2. XMLSchema validation -> on failure generate a list of XMLSchema validation errors + 3. Return all validation errors in one go + + Empty / None values return an empty list. + """ + + def _execute_operation(self): + dataset = self.evaluation_dataset + target = self.params.target + if target not in dataset: + raise KeyError(target) + try: + self.schema_xml = etree.parse( + os.path.join( + DefaultFilePaths.LOCAL_XSD_FILE_DIR.value, + DefaultFilePaths.LOCAL_XSD_FILE_MAP.value[self.params.namespace], + ) + ) + self.schema = etree.XMLSchema(self.schema_xml) + except (KeyError, OSError) as e: + raise SchemaNotFoundError(f"XSD file could not be found: {e}") + except (etree.XMLSchemaParseError, etree.XMLSyntaxError) as e: + raise InvalidSchemaProvidedError( + f"Failed to parse XMLSchema: {getattr(e, 'error_log', str(e))}" + ) + + # Build namespace declaration string from XSD namespaces + schema_nsmap = self.schema_xml.getroot().nsmap + schema_nsmap.pop("xs") + self.nsdec = " ".join( + k and f'xmlns:{k}="{v}"' or f'xmlns="{v}"' for k, v in schema_nsmap.items() + ) + if any( + k in DefaultFilePaths.LOCAL_XSD_FILE_MAP.value + for k in schema_nsmap.values() + ): + self.nsdec += ' xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="' + for k, v in DefaultFilePaths.LOCAL_XSD_FILE_MAP.value.items(): + if k in schema_nsmap.values(): + self.nsdec += "{} ../{} ".format( + k, + # Using join because schemaLocation always uses forward slashes regardless of OS + "/".join( + DefaultFilePaths.LOCAL_XSD_FILE_DIR.value.split(os.sep) + + v.split(os.sep) + ), + ) + self.nsdec += '"' + + self.line_pattern = re.compile(r"line (\d+)") + + return dataset[target].apply(self._ensure_dataset_is_valid_xhtml) + + def _ensure_dataset_is_valid_xhtml(self, value: str) -> list[str]: + value: str = value.strip() + if not value: + return [] + + text = value.strip() + if not text: + return [] + + errors = [] + + xhtml_mod, text = self._wrap_xhtml(text) + + line_labels = ( + { + 1: "(wrapper start)", + len(text.split("\n")): "(wrapper end)", + } + if xhtml_mod + else {} + ) + + parser = etree.XMLParser(recover=True, ns_clean=True) + xhtml_to_validate = etree.XML(text.encode("utf-8"), parser) + + self._report_errors( + xhtml_to_validate, parser.error_log, errors, xhtml_mod, line_labels + ) + + if not self.schema.validate(xhtml_to_validate): + self._report_errors( + xhtml_to_validate, + self.schema.error_log, + errors, + xhtml_mod, + line_labels, + ) + return errors + + def _wrap_xhtml(self, text: str) -> tuple[bool, str]: + """Wraps the input text in ... if not already present.""" + if not text.startswith("<"): + return ( + True, + f"
\n{text}\n
", + ) + if "" not in text: + return ( + True, + f"\n{text}\n", + ) + if "" not in text: + return True, ( + text.replace("", "") + if text.startswith("\n{text}\n" + ) + return False, text + + def _report_errors( + self, + xhtml: etree.ElementTree, + error_log: etree._ErrorLog, + errors: list[str], + xhtml_mod: bool = False, + line_lbls: dict = {}, + ) -> list[str]: + for error in error_log: + msg = error.message.strip() + if xhtml_mod and re.search(self.line_pattern, msg): + # Adjust line numbers in message + msg = self.line_pattern.sub( + lambda x: self._get_line_name(line_lbls, int(x.groups()[0])), + msg, + ) + + line_col = ( + ( + f"{self._get_line_name(line_lbls, error.line, error.column)}" + if xhtml_mod + else f"line {error.line}" + ) + if error.line + else "unknown pos" + ) + + if xhtml.nsmap: + for k, v in xhtml.nsmap.items(): + if v in msg: + prefix = f"{k}:" if k else "" + msg = re.sub(r"\{" + re.escape(v) + r"\}", prefix, msg) + + errors.append(f"Invalid XHTML {line_col} [{error.level_name}]: {msg}") + + def _get_line_name(self, line_labels, line: int, col: int | None = None) -> str: + return line_labels.get( + line, f"line {line - 1}" + (f", col {col}" if col else "") + ) diff --git a/cdisc_rules_engine/operations/operations_factory.py b/cdisc_rules_engine/operations/operations_factory.py index 407e4bd91..2a77adf09 100644 --- a/cdisc_rules_engine/operations/operations_factory.py +++ b/cdisc_rules_engine/operations/operations_factory.py @@ -10,6 +10,7 @@ ) from cdisc_rules_engine.operations.distinct import Distinct from cdisc_rules_engine.operations.extract_metadata import ExtractMetadata +from cdisc_rules_engine.operations.get_xhtml_errors import GetXhtmlErrors from cdisc_rules_engine.operations.library_column_order import LibraryColumnOrder from cdisc_rules_engine.operations.library_model_column_order import ( LibraryModelColumnOrder, @@ -132,6 +133,7 @@ class OperationsFactory(FactoryInterface): "valid_external_dictionary_code_term_pair": ValidExternalDictionaryCodeTermPair, "valid_define_external_dictionary_version": DefineDictionaryVersionValidator, "get_dataset_filtered_variables": GetDatasetFilteredVariables, + "get_xhtml_errors": GetXhtmlErrors, } @classmethod @@ -172,6 +174,6 @@ def get_service( kwargs.get("library_metadata"), ) raise ValueError( - f"Operation name must be in {list(self._operations_map.keys())}, " + f"Operation name must be in {list(self._operations_map.keys())}, " f"given operation name is {name}" ) diff --git a/cdisc_rules_engine/rules_engine.py b/cdisc_rules_engine/rules_engine.py index ccde2537f..94f8f7308 100644 --- a/cdisc_rules_engine/rules_engine.py +++ b/cdisc_rules_engine/rules_engine.py @@ -15,6 +15,8 @@ VariableMetadataNotFoundError, FailedSchemaValidation, DomainNotFoundError, + InvalidSchemaProvidedError, + SchemaNotFoundError, ) from cdisc_rules_engine.interfaces import ( CacheServiceInterface, @@ -442,6 +444,20 @@ def handle_validation_exceptions( # noqa message=exception.args[0], ) message = "rule execution error" + elif isinstance(exception, SchemaNotFoundError): + error_obj = FailedValidationEntity( + dataset=os.path.basename(dataset_path), + error=SchemaNotFoundError.description, + message=exception.args[0], + ) + message = "rule execution error" + elif isinstance(exception, InvalidSchemaProvidedError): + error_obj = FailedValidationEntity( + dataset=os.path.basename(dataset_path), + error=InvalidSchemaProvidedError.description, + message=exception.args[0], + ) + message = "rule execution error" elif isinstance(exception, VariableMetadataNotFoundError): error_obj = FailedValidationEntity( dataset=os.path.basename(dataset_path), diff --git a/cdisc_rules_engine/utilities/rule_processor.py b/cdisc_rules_engine/utilities/rule_processor.py index 18ad570c9..b9a8a87c5 100644 --- a/cdisc_rules_engine/utilities/rule_processor.py +++ b/cdisc_rules_engine/utilities/rule_processor.py @@ -398,6 +398,7 @@ def perform_rule_operations( term_code=operation.get("term_code"), term_value=operation.get("term_value"), term_pref_term=operation.get("term_pref_term"), + namespace=operation.get("namespace"), ) # execute operation diff --git a/requirements.txt b/requirements.txt index 31ec8e820..947ee21e7 100644 --- a/requirements.txt +++ b/requirements.txt @@ -21,4 +21,5 @@ psutil==6.1.1 dask[dataframe]==2024.6.0 dask[array]==2024.6.0 pyreadstat==1.2.7 -fastparquet==2024.2.0 \ No newline at end of file +fastparquet==2024.2.0 +lxml==5.2.1 \ No newline at end of file diff --git a/resources/schema/Operations.json b/resources/schema/Operations.json index 6af7c3b46..cdbe63c2e 100644 --- a/resources/schema/Operations.json +++ b/resources/schema/Operations.json @@ -393,6 +393,13 @@ }, "required": ["id", "operator"], "type": "object" + }, + { + "properties": { + "operator": { "const": "get_xhtml_errors" } + }, + "required": ["id", "operator", "name", "namespace"], + "type": "object" } ], "properties": { @@ -520,6 +527,9 @@ "name": { "type": "string" }, + "namespace": { + "type": "string" + }, "operator": { "type": "string" }, diff --git a/resources/schema/Operations.md b/resources/schema/Operations.md index cc34d5bda..7b77e7350 100644 --- a/resources/schema/Operations.md +++ b/resources/schema/Operations.md @@ -1233,3 +1233,17 @@ Operations: name: USUBJID id: $aeterm_is_null ``` + +### get_xhtml_errors + +Validates XHTML fragments in the target column against the specified namespace. + +```yaml +Operations: + - id: $xhtml_errors + name: text + operator: get_xhtml_errors + namespace: http://www.cdisc.org/ns/usdm/xhtml/v1.0 +``` + +Note that a local XSD file is required for validation. The file must be stored in the folder indicated by the value of the `LOCAL_XSD_FILE_DIR` default file path and the mapping between the namespace and the local XSD file's `sub-folder/name` must be included in the value of the `LOCAL_XSD_FILE_MAP` default file path. diff --git a/resources/schema/xml/cdisc-usdm-xhtml-1.0/usdm-xhtml-1.0.xsd b/resources/schema/xml/cdisc-usdm-xhtml-1.0/usdm-xhtml-1.0.xsd new file mode 100644 index 000000000..041061836 --- /dev/null +++ b/resources/schema/xml/cdisc-usdm-xhtml-1.0/usdm-xhtml-1.0.xsd @@ -0,0 +1,16 @@ + + + + + USDM-XHTML 1.0 schema as developed by the CDISC USDM Team + + + + + + \ No newline at end of file diff --git a/resources/schema/xml/cdisc-usdm-xhtml-1.0/usdm-xhtml-extension.xsd b/resources/schema/xml/cdisc-usdm-xhtml-1.0/usdm-xhtml-extension.xsd new file mode 100644 index 000000000..4829dd7e4 --- /dev/null +++ b/resources/schema/xml/cdisc-usdm-xhtml-1.0/usdm-xhtml-extension.xsd @@ -0,0 +1,30 @@ + + + + + + + USDM-XHTML 1.0 usdm-xhtml-extension schema as developed by the CDISC USDM + Team + + + + + + + + + + + + + \ No newline at end of file diff --git a/resources/schema/xml/cdisc-usdm-xhtml-1.0/usdm-xhtml-ns.xsd b/resources/schema/xml/cdisc-usdm-xhtml-1.0/usdm-xhtml-ns.xsd new file mode 100644 index 000000000..a6e7a616b --- /dev/null +++ b/resources/schema/xml/cdisc-usdm-xhtml-1.0/usdm-xhtml-ns.xsd @@ -0,0 +1,48 @@ + + + + + + + USDM-XHTML 1.0 usdm-xhtml-ns schema as developed by the CDISC USDM Team + + + + + + + + A reference to content held within the remainder of the model. + + The name of the class that holds the referenced data element. + + + The id value of the referenced instance of the referenced class. + + + The attribute name of the referenced data element within the referenced instance of the referenced class. + + + + + + + A reference to a parameter that is mapped to a value. + + The name of the referenced parameter. + + + + \ No newline at end of file diff --git a/resources/schema/xml/xhtml-1.1/aria-attributes-1.xsd b/resources/schema/xml/xhtml-1.1/aria-attributes-1.xsd new file mode 100644 index 000000000..95af334b8 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/aria-attributes-1.xsd @@ -0,0 +1,163 @@ + + + + +This is the XML Schema module for WAI-ARIA States and Properties. +It can be incorporated in host languages to help make dynamic content accessible. +A role attribute that accepts WAI-ARIA roles is also required. +$Id: aria-attributes-1.xsd,v 1.1 2009/12/10 17:04:47 cooper Exp $ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xframes-1.xsd b/resources/schema/xml/xhtml-1.1/xframes-1.xsd new file mode 100644 index 000000000..2092d31af --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xframes-1.xsd @@ -0,0 +1,166 @@ + + + + + + This is XFrames - an XML application for composing documents together. + URI: http://www.w3.org/MarkUp/SCHEMA/xframes-1.xsd + + Copyright ©2002-2005 W3C (MIT, ERCIM, Keio), All Rights Reserved. + + Editor: Masayasu Ishikawa (mimasa@w3.org) + Revision: $Id: xframes-1.xsd,v 1.9 2005/10/05 23:56:45 mimasa Exp $ + + Permission to use, copy, modify and distribute this XML Schema for + XFrames and its accompanying documentation for any purpose and without + fee is hereby granted in perpetuity, provided that the above copyright + notice and this paragraph appear in all copies. The copyright holders + make no representation about the suitability of this XML Schema + for any purpose. + + It is provided "as is" without expressed or implied warranty. + + + + + + + Get access to the XML namespace + + + + + + + Datatypes + + + + + + + media type, as per [RFC2045] + + + + + + + + + A comma-separated list of media descriptors as described by [CSS2]. + The default is all. + + + + + + + + + + + An [XMLNS]-qualified name. + + + + + + + + + An Internationalized Resource Identifier Reference, as defined + by [IRI]. + + + + + + + + + Common attributes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-access-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-access-1.xsd new file mode 100644 index 000000000..c417eec00 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-access-1.xsd @@ -0,0 +1,43 @@ + + + + + + + This is the XML Schema module for XHTML Access + $Id: xhtml-access-1.xsd,v 1.1 2008/05/17 16:21:57 smccarro Exp $ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-applet-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-applet-1.xsd new file mode 100644 index 000000000..73e66385c --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-applet-1.xsd @@ -0,0 +1,66 @@ + + + + + + + Java Applets + This is the XML Schema module for Java Applets in XHTML + + * applet (param) + + This module declares the applet element type and its attributes, + used to provide support for Java applets. The 'alt' attribute + is now required (as it is on images). One of either code or + object attributes must be present. In the document, place param + elements before the object elements that require their content. + + Note that use of this module also instantiates of the + Param Element Module. + + $Id: xhtml-applet-1.xsd,v 1.3 2005/09/26 22:54:52 ahby Exp $ + + + + + + + + + Param module + Include Param Module + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-attribs-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-attribs-1.xsd new file mode 100644 index 000000000..44336fce6 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-attribs-1.xsd @@ -0,0 +1,73 @@ + + + + + + + This is the XML Schema common attributes module for XHTML + $Id: xhtml-attribs-1.xsd,v 1.9 2009/11/18 17:59:51 ahby Exp $ + + + + + + + + This import brings in the XML namespace attributes + The module itself does not provide the schemaLocation + and expects the driver schema to provide the + actual SchemaLocation. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-base-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-base-1.xsd new file mode 100644 index 000000000..a23df79d4 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-base-1.xsd @@ -0,0 +1,36 @@ + + + + + + + Base element + This is the XML Schema Base Element module for XHTML + + * base + + This module declares the base element type and its attributes, + used to define a base URI against which relative URIs in the + document will be resolved. + + $Id: xhtml-base-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $ + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-basic-form-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-basic-form-1.xsd new file mode 100644 index 000000000..7287f402f --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-basic-form-1.xsd @@ -0,0 +1,196 @@ + + + + + + This is the XML Schema Basic Forms module for XHTML + $Id: xhtml-basic-form-1.xsd,v 1.3 2009/09/30 15:22:38 ahby Exp $ + + + + + + + Basic Forms + + This forms module is based on the HTML 3.2 forms model, with + the WAI-requested addition of the label element. While this + module essentially mimics the content model and attributes of + HTML 3.2 forms, the element types declared herein also include + all HTML 4 common attributes. + + Elements defined here: + + * form, label, input, select, option, textarea + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-basic-table-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-basic-table-1.xsd new file mode 100644 index 000000000..79bfe3459 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-basic-table-1.xsd @@ -0,0 +1,169 @@ + + + + + + This is the XML Schema Basic Tables module for XHTML + $Id: xhtml-basic-table-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $ + + + + + + + Basic Tables + + * table, caption, tr, th, td + + This table module declares elements and attributes defining + a table model based fundamentally on features found in the + widely-deployed HTML 3.2 table model. While this module + mimics the content model and table attributes of HTML 3.2 + tables, the element types declared herein also includes all + HTML 4 common and most of the HTML 4 table attributes. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-basic10-model-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-basic10-model-1.xsd new file mode 100644 index 000000000..6174903f3 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-basic10-model-1.xsd @@ -0,0 +1,385 @@ + + + + + + This is the XML Schema module of named XHTML content models for XHTML Basic 10 + $Id: xhtml-basic10-model-1.xsd,v 1.6 2006/09/11 10:14:57 ahby Exp $ + + + + + + + XHTML Basic 1.0 Document Model + + This module describes the groupings of elements/attributes that make up + common content models for XHTML elements. + + XHTML has following basic content models: + + Inline.mix; character-level elements + Block.mix; block-like elements, eg., paragraphs and lists + Flow.mix; any block or inline elements + HeadOpts.mix; Head Elements + InlinePre.mix; Special class for pre content model + InlineNoAnchor.mix; Content model for Anchor + + Any groups declared in this module may be used + to create element content models, but the above are + considered 'global' (insofar as that term applies here). + + XHTML has the following Attribute Groups + Core.extra.attrib + I18n.extra.attrib + Common.extra + + The above attribute Groups are considered Global + + + + + + + + Extended I18n attribute + + + + + + + + Extended Core Attributes + + + + + + + + Extended Common Attributes + + + + + + + + Extended Global Core Attributes + + + + + + + + Extended Global I18n attributes + + + + + + + + Extended Global Common Attributes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-basic10-module-redefines-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-basic10-module-redefines-1.xsd new file mode 100644 index 000000000..319c79a3a --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-basic10-module-redefines-1.xsd @@ -0,0 +1,61 @@ + + + + + + This XML Schema declares changes to the content models + of modules included in XHTML Basic1.0 + $Id: xhtml-basic10-module-redefines-1.xsd,v 1.1 2003/09/23 21:12:52 speruvem Exp $ + + + + + + + Module Content Model Redefinitions + + This schema describes the changes (Redefinitions) to + content model of individual modules as they are instantiated as part of + XHTML Basic 1.0 Document + + + + + + + + + + Redefinition by Base module + + + + + + + + + + + + + + + + + + + + + + + + Redefinition by the XHTML11 Markup (for value of version attr) + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-basic10-modules-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-basic10-modules-1.xsd new file mode 100644 index 000000000..83ccc869e --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-basic10-modules-1.xsd @@ -0,0 +1,233 @@ + + + + + + + This schema includes all modules for XHTML Basic 1.0 Document Type. + $Id: xhtml-basic10-modules-1.xsd,v 1.3 2005/09/26 22:54:53 ahby Exp $ + + + + + + + This schema includes all modules (and redefinitions) + for XHTML Basic 1.0 Document Type. + XHTML Basic 1.0 Document Type includes the following Modules + + XHTML Core modules (Required for XHTML Family Conformance) + + text + + hypertext + + lists + + structure + + Other XHTML modules + + Link + + Meta + + Base + + Image + + Object + + Param + + Basic forms + + Basic tables + + + + + + + Schema Framework Component Modules: + + notations + + datatypes + + common attributes + + character entities + + + + + + + + + Text module + + The Text module includes declarations for all core + text container elements and their attributes. + + + block phrasal + + block structural + + inline phrasal + + inline structural + + Elements defined here: + * address, blockquote, pre, h1, h2, h3, h4, h5, h6 + * div, p + * abbr, acronym, cite, code, dfn, em, kbd, q, samp, strong, var + * br, span + + + + + + + + + Hypertext module + + Elements defined here: + * a + + + + + + + + + Lists module + + Elements defined here: + * dt, dd, dl, ol, ul, li + + + + + + + + + Structural module + + Elements defined here: + * title, head, body, html + + + + + + + Redefinition by the XHTML11 Markup (for value of version attr) + + + + + + + + + + Link module + + Elements defined here: + * link + + + + + + + + + Meta module + + Elements defined here: + * meta + + + + + + + + + Base module + + Elements defined here: + * base + + + + + + + + + Image module + + Elements defined here: + * img + + + + + + + + + Object module + + Elements defined here: + * object + + + + + + + + + Param module + + Elements defined here: + * param + + + + + + + + Basic Forms module + + Note that this module is not used in XHTML 1.1. It is designed + for use with XHTML Basic + + Elements defined here: + * form, label, input, select, option, textarea + + + + + + + + + Basic Tables module + + Note that this module is not used in XHTML It is designed + for use with XHTML Basic + + Elements defined here: + * table, caption, tr, th, td + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-basic10.xsd b/resources/schema/xml/xhtml-1.1/xhtml-basic10.xsd new file mode 100644 index 000000000..eea3b5425 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-basic10.xsd @@ -0,0 +1,99 @@ + + + + + + This is the XML Schema driver for XHTML Basic 1.0. + Please use this namespace for XHTML elements: + "http://www.w3.org/1999/xhtml" + + $Id: xhtml-basic10.xsd,v 1.7 2005/09/26 22:54:53 ahby Exp $ + + + + + + This is XHTML, a reformulation of HTML as a modular XML application + The Extensible HyperText Markup Language (XHTML) + Copyright ©1998-2005 World Wide Web Consortium + (Massachusetts Institute of Technology, European Research Consortium + for Informatics and Mathematics, Keio University). + All Rights Reserved. + + Permission to use, copy, modify and distribute the XHTML Schema + modules and their accompanying xs:documentation for any purpose + and without fee is hereby granted in perpetuity, provided that the above + copyright notice and this paragraph appear in all copies. + The copyright holders make no representation about the suitability of + these XML Schema modules for any purpose. + + They are provided "as is" without expressed or implied warranty. + + + + + + This is the Schema Driver file for XHTML Basic 1.0 + Document Type + + This schema includes + + imports external schemas (xml.xsd) + + refedines (and include)s schema modules for XHTML + Basic 1.0 Document Type. + + includes Schema for Named content model for the + XHTML Basic 1.0 Document Type + + XHTML Basic 1.0 Document Type includes the following Modules + + XHTML Core modules (Required for XHTML Family Conformance) + + text + + hypertext + + lists + + structure (redefined) + + Other XHTML modules + + Link + + Meta + + Base + + Image + + Object + + Param + + Basic forms + + Basic tables + + + + + + + This import brings in the XML namespace attributes + The XML attributes are used by various modules + + + + + + + + Document Model module for the XHTML Basic 1.0 Document Type + This schema file defines all named models used by XHTML + Modularization Framework for XHTML Basic 1.0 Document Type + + + + + + + + Schema that includes the modules (and redefinitions) + for XHTML Basic 1.0 Document Type. + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-basic11-model-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-basic11-model-1.xsd new file mode 100644 index 000000000..1f8ca8460 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-basic11-model-1.xsd @@ -0,0 +1,639 @@ + + + + + + + This is the XML Schema module of named XHTML content models for XHTML Basic 10 + $Id: xhtml-basic11-model-1.xsd,v 1.3 2009/11/18 20:54:34 smccarro Exp $ + + + + + + + XHTML Basic 1.1 Document Model + + This module describes the groupings of elements/attributes + that make up common content models for XHTML elements. + XHTML has following basic content models: + xhtml.Inline.mix; character-level elements + xhtml.Block.mix; block-like elements, e.g., paragraphs and lists + xhtml.Flow.mix; any block or inline elements + xhtml.HeadOpts.mix; Head Elements + xhtml.InlinePre.mix; Special class for pre content model + xhtml.InlineNoAnchor.mix; Content model for Anchor + + Any groups declared in this module may be used to create + element content models, but the above are considered 'global' + (insofar as that term applies here). XHTML has the + following Attribute Groups + xhtml.Core.extra.attrib + xhtml.I18n.extra.attrib + xhtml.Common.extra + + The above attribute Groups are considered Global + + + + + Extended I18n attribute + + + + + + Extended Common Attributes + + + + + "style" attribute from Inline Style Module + + + + + + + Attributes from Events Module + + + + + + + Extend Core Attributes + + + + + Extended Global Core Attributes + + + + + Extended Global I18n attributes + + + + + Extended Global Common Attributes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-basic11-modules-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-basic11-modules-1.xsd new file mode 100644 index 000000000..b10278f8f --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-basic11-modules-1.xsd @@ -0,0 +1,508 @@ + + + + + + + This schema includes all modules for XHTML Basic 1.1 Document Type. + $Id: xhtml-basic11-modules-1.xsd,v 1.4 2009/11/18 20:54:36 smccarro Exp $ + + + + + + + This schema includes all modules (and redefinitions) + for XHTML Basic 1.1 Document Type. + XHTML Basic 1.1 Document Type includes the following Modules + + XHTML Core modules (Required for XHTML Family Conformance) + + text + + hypertext + + lists + + structure + + Other XHTML modules + + Link + + Meta + + Base + + Image + + Object + + Param + + Basic forms + + Basic tables + + + + + + + Schema Framework Component Modules: + + notations + + datatypes + + common attributes + + character entities + + + + + + + + Text module + + The Text module includes declarations for all core + text container elements and their attributes. + + + block phrasal + + block structural + + inline phrasal + + inline structural + + Elements defined here: + * address, blockquote, pre, h1, h2, h3, h4, h5, h6 + * div, p + * abbr, acronym, cite, code, dfn, em, kbd, q, samp, strong, var + * br, span + + + + + + + + Hypertext module + + Elements defined here: + * a + + + + + + + + + Redefinition by XHTML Event Attribute Module + + + + + + + Target Module - A Attribute Additions + + + + + + + + + Lists module + + Elements defined here: + * dt, dd, dl, ol, ul, li + + + + + + + + + + + + Structural module + + Elements defined here: + * title, head, body, html + + + + + + + Redefinition by the XHTML11 Markup (for value of version attr) + + + + + + + + + Original Body Attlist + + + + + + + Redefinition by XHTML Event Attribute Module + + + + + + + + + Presentational module + + Elements defined here: + * hr, b, big, i, small,sub, sup, tt + + + + + + + + Link module + + Elements defined here: + * link + + + + + + + Changes to XHTML Link Attlist + + + + + + Original Link Attributes (declared in Link Module) + + + + + + + XHTML Target Module - Attribute additions + + + + + + + + + Meta module + + Elements defined here: + * meta + + + + + + + + Base module + + Elements defined here: + * base + + + + + + + Changes to XHTML base Attlist + + + + + + Original Base Attributes (declared in Base Module) + + + + + + + XHTML Target Module - Attribute additions + + + + + + + + + Scripting module + + Elements defined here: + * script, noscript + + + + + + + + Style module + + Elements defined here: + * style + + + + + + + + Style attribute module + + Attribute defined here: + * style + + + + + + + + Image module + + Elements defined here: + * img + + + + + + + + Original Image Attributes (in Image Module) + + + + + + + + + Object module + + Elements defined here: + * object + + + + + + + + Original Object Attlist + + + + + + + + + Param module + + Elements defined here: + * param + + + + + + + Basic Tables module + + Note that this module is not used in XHTML It is designed + for use with XHTML Basic + + Elements defined here: + * table, caption, tr, th, td + + + + + + + + Forms module + + Elements defined here: + * form, label, input, select, optgroup, option, + * textarea, fieldset, legend, button + + + + + + + Changes to XHTML Form Attlist + + + + + + Original Form Attributes (declared in Forms Module) + + + + + + + XHTML Events Module - Attribute additions + + + + + + + XHTML Target Module - Attribute additions + + + + + + + + Changes to XHTML Form Input Element + + + + + + Original Input Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + Redefinition by Inputmode Attribute Module + + + + + + + + + Original Label Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + Original Select Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + Original TextArea Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + Redefinition by Inputmode Attribute Module + + + + + + + + + Original Button Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + XHTML Events Modules + + Attributes defined here: + XHTML Event Types + + + + + + + + XHTML Target Attribute Module + + Attributes defined here: + target + + + + + + + + XHTML Inputmode Module + + Attributes defined here: + inputmode + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-basic11.xsd b/resources/schema/xml/xhtml-1.1/xhtml-basic11.xsd new file mode 100644 index 000000000..031fa1b92 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-basic11.xsd @@ -0,0 +1,105 @@ + + + + + + This is the XML Schema driver for XHTML Basic 1.1. + Please use this namespace for XHTML elements: + "http://www.w3.org/1999/xhtml" + + $Id: xhtml-basic11.xsd,v 1.3 2009/11/18 20:54:38 smccarro Exp $ + + + + + + This is XHTML Basic + Copyright ©1998-2008 World Wide Web Consortium + (Massachusetts Institute of Technology, European Research Consortium + for Informatics and Mathematics, Keio University). + All Rights Reserved. + + Permission to use, copy, modify and distribute the XHTML Schema + modules and their accompanying xs:documentation for any purpose + and without fee is hereby granted in perpetuity, provided that the above + copyright notice and this paragraph appear in all copies. + The copyright holders make no representation about the suitability of + these XML Schema modules for any purpose. + + They are provided "as is" without expressed or implied warranty. + + + + + + This is the Schema Driver file for XHTML Basic 1.1 + Document Type + + This schema includes + + imports external schemas (xml.xsd) + + refedines (and include)s schema modules for XHTML + Basic 1.1 Document Type. + + includes Schema for Named content model for the + XHTML Basic 1.1 Document Type + + XHTML Basic 1.1 Document Type includes the following Modules + + XHTML Core modules (Required for XHTML Family Conformance) + + text + + hypertext + + lists + + structure (redefined) + + Other XHTML modules + + Link + + Metainformation + + Intrinsic Events + + Scripting + + Stylesheet + + Style Attribute + + Target + + Inputmode + + Base + + Image + + Object + + Presentation + + Param + + Forms + + Basic tables + + + + + + + This import brings in the XML namespace attributes + The XML attributes are used by various modules + + + + + + + + Document Model module for the XHTML Basic 1.1 Document Type + This schema file defines all named models used by XHTML + Modularization Framework for XHTML Basic 1.1 Document Type + + + + + + + + Schema that includes the modules (and redefinitions) + for XHTML Basic 1.1 Document Type. + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-bdo-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-bdo-1.xsd new file mode 100644 index 000000000..1d8dc08d7 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-bdo-1.xsd @@ -0,0 +1,71 @@ + + + + + + Bidirectional Override (bdo) Element + This is the XML Schema BDO Element module for XHTML + + This modules declares the element 'bdo' and 'dir' attributes, + Used to override the Unicode bidirectional algorithm for selected + fragments of text. + Bidirectional text support includes both the bdo element and + the 'dir' attribute. + + $Id: xhtml-bdo-1.xsd,v 1.6 2009/11/18 17:59:51 ahby Exp $ + + + + + + + + This import brings in the XML namespace attributes + The module itself does not provide the schemaLocation + and expects the driver schema to provide the + actual SchemaLocation. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-blkphras-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-blkphras-1.xsd new file mode 100644 index 000000000..89938b4c0 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-blkphras-1.xsd @@ -0,0 +1,160 @@ + + + + + + + + + This is the XML Schema Block Phrasal support module for XHTML + $Id: xhtml-blkphras-1.xsd,v 1.7 2008/07/05 04:11:00 ahby Exp $ + + + + + + Block Phrasal + This module declares the elements and their attributes used to + support block-level phrasal markup. + This is the XML Schema block phrasal elements module for XHTML + + * address, blockquote, pre, h1, h2, h3, h4, h5, h6 + + + + + + + This import brings in the XML namespace attributes + The module itself does not provide the schemaLocation + and expects the driver schema to provide the + actual SchemaLocation. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-blkpres-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-blkpres-1.xsd new file mode 100644 index 000000000..cf42303a6 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-blkpres-1.xsd @@ -0,0 +1,37 @@ + + + + + + This is the XML SchemaBlock presentation element module for XHTML + $Id: xhtml-blkpres-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $ + + + + + Block Presentational Elements + + * hr + + This module declares the elements and their attributes used to + support block-level presentational markup. + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-blkstruct-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-blkstruct-1.xsd new file mode 100644 index 000000000..1e658580e --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-blkstruct-1.xsd @@ -0,0 +1,49 @@ + + + + + + Block Structural + + * div, p + + This module declares the elements and their attributes used to + support block-level structural markup. + + This is the XML Schema Block Structural module for XHTML + $Id: xhtml-blkstruct-1.xsd,v 1.3 2005/09/26 22:54:53 ahby Exp $ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-charent-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-charent-1.xsd new file mode 100644 index 000000000..06029e7cb --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-charent-1.xsd @@ -0,0 +1,38 @@ + + + + + %HTMLlat1; + + + %HTMLsymbol; + + + %HTMLspecial; +]> + + + + Character Entities for XHTML + This is the XML Schema Character Entities module for XHTML + + This module declares the set of character entities for XHTML, + including the Latin 1, Symbol and Special character collections. + XML Schema does not support Entities, hence Entities are enable + through an Internal DTD Subset. + + $Id: xhtml-charent-1.xsd,v 1.3 2005/09/26 22:54:53 ahby Exp $ + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-copyright-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-copyright-1.xsd new file mode 100644 index 000000000..24c84fd47 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-copyright-1.xsd @@ -0,0 +1,29 @@ + + + + + + This is XHTML, a reformulation of HTML as a modular XML application + The Extensible HyperText Markup Language (XHTML) + Copyright ©1998-2005 World Wide Web Consortium + (Massachusetts Institute of Technology, European Research Consortium + for Informatics and Mathematics, Keio University). + All Rights Reserved. + + Permission to use, copy, modify and distribute the XHTML Schema + modules and their accompanying xs:documentation for any purpose + and without fee is hereby granted in perpetuity, provided that the above + copyright notice and this paragraph appear in all copies. + The copyright holders make no representation about the suitability of + these XML Schema modules for any purpose. + + They are provided "as is" without expressed or implied warranty. + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-csismap-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-csismap-1.xsd new file mode 100644 index 000000000..42f802d0f --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-csismap-1.xsd @@ -0,0 +1,96 @@ + + + + + + + Client-side Image Maps + This is the XML Schema Client-side Image Maps module for XHTML + + * area, map + + This module declares elements and attributes to support client-side + image maps. + + $Id: xhtml-csismap-1.xsd,v 1.3 2009/09/30 15:12:48 ahby Exp $ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-datatypes-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-datatypes-1.xsd new file mode 100644 index 000000000..ab7bac0ee --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-datatypes-1.xsd @@ -0,0 +1,242 @@ + + + + + XHTML Datatypes + This is the XML Schema datatypes module for XHTML + + Defines containers for the XHTML datatypes, many of + these imported from other specifications and standards. + + $Id: xhtml-datatypes-1.xsd,v 1.12 2009/09/30 15:12:48 ahby Exp $ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-edit-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-edit-1.xsd new file mode 100644 index 000000000..44380b23e --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-edit-1.xsd @@ -0,0 +1,39 @@ + + + + + + + Editing Elements + This is the XML Schema Editing Markup module for XHTML + + * ins, del + + This module declares element types and attributes used to indicate + inserted and deleted content while editing a document. + + $Id: xhtml-edit-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $ + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-events-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-events-1.xsd new file mode 100644 index 000000000..381f6dd50 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-events-1.xsd @@ -0,0 +1,130 @@ + + + + + + + This is the XML Schema Intrinsic Events module for XHTML + $Id: xhtml-events-1.xsd,v 1.4 2005/09/26 22:54:53 ahby Exp $ + + + + + + Intrinsic Event Attributes + These are the event attributes defined in HTML 4, + Section 18.2.3 "Intrinsic Events". + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-form-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-form-1.xsd new file mode 100644 index 000000000..d7a970f4f --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-form-1.xsd @@ -0,0 +1,327 @@ + + + + + + + Forms + This is the XML Schema Forms module for XHTML + + * form, label, input, select, optgroup, option, + textarea, fieldset, legend, button + + This module declares markup to provide support for online + forms, based on the features found in HTML 4.0 forms. + + + $Id: xhtml-form-1.xsd,v 1.4 2009/09/30 15:22:38 ahby Exp $ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-frames-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-frames-1.xsd new file mode 100644 index 000000000..897bf13bc --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-frames-1.xsd @@ -0,0 +1,113 @@ + + + + + + This is the XML Schema Frames module for XHTML + $Id: xhtml-frames-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $ + + + + + + + Frames + + * frameset, frame, noframes + + This module declares frame-related element types and attributes. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-framework-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-framework-1.xsd new file mode 100644 index 000000000..05b906d44 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-framework-1.xsd @@ -0,0 +1,66 @@ + + + + + This is the XML Schema Modular Framework support module for XHTML + $Id: xhtml-framework-1.xsd,v 1.5 2005/09/26 23:37:47 ahby Exp $ + + + + + + XHTML Modular Framework + This required module instantiates the necessary modules + needed to support the XHTML modularization framework. + + The Schema modules instantiated are: + + notations + + datatypes + + common attributes + + character entities + + + + + + + + This module defines XHTML Attribute DataTypes + + + + + + + + This module defines Common attributes for XHTML + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-hypertext-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-hypertext-1.xsd new file mode 100644 index 000000000..2f4c81bc8 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-hypertext-1.xsd @@ -0,0 +1,47 @@ + + + + + + + Hypertext Module + This is the XML Schema Hypertext module for XHTML + + * a + + This module declares the anchor ('a') element type, which + defines the source of a hypertext link. The destination + (or link 'target') is identified via its 'id' attribute + rather than the 'name' attribute as was used in HTML. + + $Id: xhtml-hypertext-1.xsd,v 1.4 2005/09/26 23:37:47 ahby Exp $ + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-iframe-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-iframe-1.xsd new file mode 100644 index 000000000..c9b451939 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-iframe-1.xsd @@ -0,0 +1,68 @@ + + + + + + This is the XML Schema Inline Frame Element module for XHTML + $Id: xhtml-iframe-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $ + + + + + + + Inline Frames + + * iframe + + This module declares the iframe element type and its attributes, + used to create an inline frame within a document. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-image-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-image-1.xsd new file mode 100644 index 000000000..4d6e9ab16 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-image-1.xsd @@ -0,0 +1,46 @@ + + + + + + + Images + This is the XML Schema Images module for XHTML + + * img + + This module provides markup to support basic image embedding. + + To avoid problems with text-only UAs as well as to make + image content understandable and navigable to users of + non-visual UAs, you need to provide a description with + the 'alt' attribute, and avoid server-side image maps. + + + $Id: xhtml-image-1.xsd,v 1.3 2009/09/30 15:22:38 ahby Exp $ + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-inlphras-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-inlphras-1.xsd new file mode 100644 index 000000000..919c59de3 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-inlphras-1.xsd @@ -0,0 +1,163 @@ + + + + + + + This is the XML Schema Inline Phrasal support module for XHTML + $Id: xhtml-inlphras-1.xsd,v 1.4 2005/09/26 22:54:53 ahby Exp $ + + + + + + Inline Phrasal. + This module declares the elements and their attributes used to + support inline-level phrasal markup. + This is the XML Schema Inline Phrasal module for XHTML + + * abbr, acronym, cite, code, dfn, em, kbd, q, samp, strong, var + + $Id: xhtml-inlphras-1.xsd,v 1.4 2005/09/26 22:54:53 ahby Exp $ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-inlpres-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-inlpres-1.xsd new file mode 100644 index 000000000..a053447c2 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-inlpres-1.xsd @@ -0,0 +1,39 @@ + + + + + + This is the XML Schema Inline Presentation element module for XHTML + $Id: xhtml-inlpres-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $ + + + + + + Inline Presentational Elements + + * b, big, i, small, sub, sup, tt + + This module declares the elements and their attributes used to + support inline-level presentational markup. + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-inlstruct-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-inlstruct-1.xsd new file mode 100644 index 000000000..635eb5f19 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-inlstruct-1.xsd @@ -0,0 +1,50 @@ + + + + + + This is the XML Schema Inline Structural support module for XHTML + $Id: xhtml-inlstruct-1.xsd,v 1.4 2005/09/26 22:54:53 ahby Exp $ + + + + + + Inline Structural. + This module declares the elements and their attributes + used to support inline-level structural markup. + This is the XML Schema Inline Structural element module for XHTML + + * br, span + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-inlstyle-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-inlstyle-1.xsd new file mode 100644 index 000000000..ef93c2dce --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-inlstyle-1.xsd @@ -0,0 +1,27 @@ + + + + + + Inline Style module + This is the XML Schema Inline Style module for XHTML + + * styloe attribute + + This module declares the 'style' attribute, used to support inline + style markup. + + $Id: xhtml-inlstyle-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $ + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-inputmode-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-inputmode-1.xsd new file mode 100644 index 000000000..16c67cd84 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-inputmode-1.xsd @@ -0,0 +1,35 @@ + + + + + + This is the XML Schema inputmode module for XHTML + $Id: xhtml-inputmode-1.xsd,v 1.3 2009/11/18 20:54:42 smccarro Exp $ + + + + + + + InputMode + + * inputmode + + This module declares the 'inputmode' attribute used for giving hints about how to deal with input + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-legacy-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-legacy-1.xsd new file mode 100644 index 000000000..c340bc100 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-legacy-1.xsd @@ -0,0 +1,97 @@ + + + + + + This is the XML Schema Module for HTML Legacy Markup + + font, basefont, center, s, strike, u, + dir, menu, isindex + (plus additional datatypes and legacy attributes) + + This optional module declares additional markup for simple + presentation-related markup based on features found in the + HTML 4 Transitional and Frameset DTDs. + + The legacy module also include frames module, iframe module + and target module. (Note: This module expects find the schema files + of that declare these module) + + Elements/Attributes defined in frame, iframe and target modules are + + * frameset, frame, noframes, att:target, iframe + + $Id: xhtml-legacy-1.xsd,v 1.3 2009/09/30 15:29:49 ahby Exp $ + + + + + + + + + + + + Miscellaneous module + Attributes defined here: + + * font, basefont, center, s, strike, u, dir, menu, isindex + (plus additional datatypes and attributes) + + + + + + + + + Frames module + + Elements defined here: + + * frameset, frame, noframes + + + + + + + + + Target module + + Attributes defined here: + + * target + + + + + + + + + Iframe module + + Elements defined here: + + * iframe + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-link-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-link-1.xsd new file mode 100644 index 000000000..f210d84a1 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-link-1.xsd @@ -0,0 +1,45 @@ + + + + + + This is the XML Schema Link Element module for XHTML + $Id: xhtml-link-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $ + + + + + + Link element + + * link + + This module declares the link element type and its attributes, + which could (in principle) be used to define document-level links + to external resources. + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-list-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-list-1.xsd new file mode 100644 index 000000000..cc22ba88f --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-list-1.xsd @@ -0,0 +1,99 @@ + + + + + + List Module + This is the XML Schema Lists module for XHTML + List Module Elements + + * dl, dt, dd, ol, ul, li + + This module declares the list-oriented element types + and their attributes. + $Id: xhtml-list-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-meta-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-meta-1.xsd new file mode 100644 index 000000000..b50a21ddc --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-meta-1.xsd @@ -0,0 +1,54 @@ + + + + + + + This is the XML Schema Metainformation module for XHTML + $Id: xhtml-meta-1.xsd,v 1.3 2008/07/05 04:11:00 ahby Exp $ + + + + + + Meta Information + + * meta + + This module declares the meta element type and its attributes, + used to provide declarative document metainformation. + + + + + + + This import brings in the XML namespace attributes + The module itself does not provide the schemaLocation + and expects the driver schema to provide the + actual SchemaLocation. + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-metaAttributes-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-metaAttributes-1.xsd new file mode 100644 index 000000000..cdd608d65 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-metaAttributes-1.xsd @@ -0,0 +1,44 @@ + + + + + + This is the XML Schema Metainformation Attributes module for XHTML + + $Id: xhtml-metaAttributes-1.xsd,v 1.6 2008/07/05 04:15:30 smccarro Exp $ + + + + + + + XHTML Metainformation Attributes + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-metaAttributes-2.xsd b/resources/schema/xml/xhtml-1.1/xhtml-metaAttributes-2.xsd new file mode 100644 index 000000000..74230fcc0 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-metaAttributes-2.xsd @@ -0,0 +1,50 @@ + + + + + + This is the XML Schema Metainformation Attributes module for XHTML + + $Id: xhtml-metaAttributes-2.xsd,v 1.5 2015/11/24 13:10:17 smccarro Exp $ + + + + + + + XHTML Metainformation Attributes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-misc-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-misc-1.xsd new file mode 100644 index 000000000..afb43f717 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-misc-1.xsd @@ -0,0 +1,441 @@ + + + + + + This is the XML Schema Miscellaneous Legacy + Markup module for XHTML + $Id: xhtml-misc-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $ + + + + + + + XHTML Miscellaneous Legacy Markup + font, basefont, center, s, strike, u, + dir, menu, isindex + + This is to allow XHTML documents to be transformed for + display on HTML browsers where CSS support is inconsistent + or unavailable. + + The module also declares legacy attributes for elements + in other module. Note: This module only declares the + attribute list, and it is up to the document type to + redefine the model of affected modules. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Attribute redefinitions + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-nameident-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-nameident-1.xsd new file mode 100644 index 000000000..6e90bc2d4 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-nameident-1.xsd @@ -0,0 +1,54 @@ + + + + + + This is the XML Schema Name Identifier module for XHTML + $Id: xhtml-nameident-1.xsd,v 1.3 2009/09/30 15:22:38 ahby Exp $ + + + + + + + Name Identifier + + * 'name' attribute on form, img, a, map, applet, frame, iframe + + This module declares the 'name' attribute on element types when + it is used as a node identifier for legacy linking and scripting + support. This does not include those instances when 'name' is used + as a container for form control, property or metainformation names. + + This module should be instantiated following all modules it modifies. + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-notations-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-notations-1.xsd new file mode 100644 index 000000000..8ca35cd6f --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-notations-1.xsd @@ -0,0 +1,69 @@ + + + + + + Notations module + This is the XML Schema module for data type notations for XHTML + $Id: xhtml-notations-1.xsd,v 1.5 2005/09/26 22:54:53 ahby Exp $ + + + + + + Notations module + Defines the XHTML notations, many of these imported from + other specifications and standards. When an existing FPI is + known, it is incorporated here. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-object-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-object-1.xsd new file mode 100644 index 000000000..a32efb0fa --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-object-1.xsd @@ -0,0 +1,76 @@ + + + + + + + This is the XML Schema Embedded Object module for XHTML + $Id: xhtml-object-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $ + + + + + + This module declares the object element type and its attributes, + used to embed external objects as part of XHTML pages. In the + document, place param elements prior to the object elements + that require their content. + + Note that use of this module requires instantiation of the + Param Element Module prior to this module. + + Elements defined here: + + * object (param) + + + + + + + Param module + + Elements defined here: + * param + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-param-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-param-1.xsd new file mode 100644 index 000000000..ba34ff412 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-param-1.xsd @@ -0,0 +1,51 @@ + + + + + + This is the XML Schema Param Element module for XHTML + $Id: xhtml-param-1.xsd,v 1.3 2005/09/26 22:54:53 ahby Exp $ + + + + + + Parameters for Java Applets and Embedded Objects + + * param + + This module provides declarations for the param element, + used to provide named property values for the applet + and object elements. + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-pres-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-pres-1.xsd new file mode 100644 index 000000000..bc36fc48f --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-pres-1.xsd @@ -0,0 +1,51 @@ + + + + + + This is the XML Schema Presentation module for XHTML + This is a REQUIRED module. + $Id: xhtml-pres-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $ + + + + + + Presentational Elements + + This module defines elements and their attributes for + simple presentation-related markup. + + Elements defined here: + + * hr + * b, big, i, small, sub, sup, tt + + + + + + + Block Presentational module + Elements defined here: + + * hr + + + + + + + Inline Presentational module + Elements defined here: + + * b, big, i, small, sub, sup, tt + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-print-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-print-1.xsd new file mode 100644 index 000000000..9f33b7b96 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-print-1.xsd @@ -0,0 +1,85 @@ + + + + + This is the XML Schema driver for XHTML Print 1.0 + Please use this namespace for XHTML elements: + + "http://www.w3.org/1999/xhtml" + + $Id: xhtml-print-1.xsd,v 1.2 2009/11/18 19:21:31 smccarro Exp $ + + + + + + This is the Schema Driver file for XHTML Print 1.0 + Document Type + + This schema + + imports external schemas (xml.xsd) + + refedines (and include)s schema modules for XHTML1.1 Document Type. + + includes Schema for Named content model for the + XHTML Print 1.0 Document Type + + XHTML Print 1.0 Document Type includes the following Modules + XHTML Core modules (Required for XHTML Family Conformance) + + text + + hypertext + + lists + + structure + Other XHTML modules + + Edit + + Bdo + + Presentational + + Link + + Meta + + Base + + Scripting + + Style + + Image + + Applet + + Object + + Param (Applet/Object modules require Param Module) + + Basic Tables + + Basic Forms + + + + + + This import brings in the XML namespace attributes + The XML attributes are used by various modules. + + + + + + + Document Model module for the XHTML Print 1.0 Document Type. + This schema file defines all named models used by XHTML + Modularization Framework for XHTML Print 1.0 Document Type + + + + + + + + Schema that includes all modules (and redefinitions) + for XHTML Print Document Type. + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-print-model-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-print-model-1.xsd new file mode 100644 index 000000000..a9c9790ce --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-print-model-1.xsd @@ -0,0 +1,616 @@ + + + + + + This is the XML Schema module of common content models for XHTML Print 1.0 + + $Id: xhtml-print-model-1.xsd,v 1.2 2009/11/18 19:21:33 smccarro Exp $ + + + + + + XHTML Document Model + This module describes the groupings of elements/attributes + that make up common content models for XHTML elements. + XHTML has following basic content models: + xhtml.Inline.mix; character-level elements + xhtml.Block.mix; block-like elements, e.g., paragraphs and lists + xhtml.Flow.mix; any block or inline elements + xhtml.HeadOpts.mix; Head Elements + xhtml.InlinePre.mix; Special class for pre content model + xhtml.InlineNoAnchor.mix; Content model for Anchor + + Any groups declared in this module may be used to create + element content models, but the above are considered 'global' + (insofar as that term applies here). XHTML has the + following Attribute Groups + xhtml.Core.extra.attrib + xhtml.I18n.extra.attrib + xhtml.Common.extra + + The above attribute Groups are considered Global + + + + + Extended I18n attribute + + + + + Extended Common Attributes + + + + + "style" attribute from Inline Style Module + + + + + + + Extend Core Attributes + + + + + Extended Global Core Attributes + + + + + Extended Global I18n attributes + + + + + Extended Global Common Attributes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-print-modules-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-print-modules-1.xsd new file mode 100644 index 000000000..ece8635d4 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-print-modules-1.xsd @@ -0,0 +1,364 @@ + + + + + + + This schema includes all modules for XHTML1.1 Document Type. + $Id: xhtml-print-modules-1.xsd,v 1.3 2009/11/18 19:21:35 smccarro Exp $ + + + + + + This schema includes all modules (and redefinitions) + for XHTML1.1 Document Type. + XHTML1.1 Document Type includes the following Modules + + XHTML Core modules (Required for XHTML Family Conformance) + + text + + hypertext + + lists + + structure + + Other XHTML modules + + Edit + + Presentational + + Link + + Meta + + Base + + Scripting + + Style + + Image + + Object + + Param (Applet/Object modules require Param Module) + + Basic Tables + + Target + + Basic Forms + + + + + + + Schema Framework Component Modules: + + notations + + datatypes + + common attributes + + character entities + + + + + + + + Text module + + The Text module includes declarations for all core + text container elements and their attributes. + + + block phrasal + + block structural + + inline phrasal + + inline structural + + Elements defined here: + * address, blockquote, pre, h1, h2, h3, h4, h5, h6 + * div, p + * abbr, acronym, cite, code, dfn, em, kbd, q, samp, strong, var + * br, span + + + + + + + + Hypertext module + + Elements defined here: + * a + + + + + + + + + + + Lists module + + Elements defined here: + * dt, dd, dl, ol, ul, li + + + + + + + + Structural module + + Elements defined here: + * title, head, body, html + + + + + + + Redefinition by the XHTML Print 1.0 Markup (for value of version attr) + + + + + + + + + Original Body Attlist + + + + + + + + + Presentational module + + Elements defined here: + * hr, b, big, i, small,sub, sup, tt + + + + + + + + Link module + + Elements defined here: + * link + + + + + + + Changes to XHTML Link Attlist + + + + + + Original Link Attributes (declared in Link Module) + + + + + + + + + Meta module + + Elements defined here: + * meta + + + + + + + + Base module + + Elements defined here: + * base + + + + + + + Changes to XHTML base Attlist + + + + + + Original Base Attributes (declared in Base Module) + + + + + + + + + Scripting module + + Elements defined here: + * script, noscript + + + + + + + + Style module + + Elements defined here: + * style + + + + + + + + Style attribute module + + Attribute defined here: + * style + + + + + + + + Image module + + Elements defined here: + * img + + + + + + + + Original Image Attributes (in Image Module) + + + + + + + + + Object module + + Elements defined here: + * object + + + + + + + + Original Object Attlist + + + + + + + + + Param module + + Elements defined here: + * param + + + + + + + Tables module + + Elements defined here: + * table, caption, tr, th, td + + + + + + + + Forms module + + Elements defined here: + * form, label, input, select, option, + * textarea + + + + + + + Changes to XHTML Form Attlist + + + + + + Original Form Attributes (declared in Forms Module) + + + + + + + + Changes to XHTML Form Input Element + + + + + + Original Input Attributes (in Forms Module) + + + + + + + + + Original Label Attributes (in Forms Module) + + + + + + + + + Original Select Attributes (in Forms Module) + + + + + + + + + Original TextArea Attributes (in Forms Module) + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-rdfa-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-rdfa-1.xsd new file mode 100644 index 000000000..ca7e3bbf8 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-rdfa-1.xsd @@ -0,0 +1,121 @@ + + + + This is the XML Schema driver for XHTML + RDFa Please use this namespace + for XHTML elements: "http://www.w3.org/1999/xhtml" $Id: xhtml-rdfa-1.xsd,v 1.2 + 2008/07/02 13:26:46 ahby Exp $ + + + + This is the Schema Driver file for XHTML + RDFa Document Type This schema + + imports external schemas (xml.xsd) + refedines (and include)s schema modules for + XHTML1.1 Document Type. + includes Schema for Named content model for the XHTML1.1 + Document Type XHTML1.1 Document Type includes the following Modules XHTML Core modules + (Required for XHTML Family Conformance) + text + hypertext + lists + structure Other + XHTML modules + Edit + Bdo + Presentational + Link + Meta + Base + Scripting + Style + + Image + Applet + Object + Param (Applet/Object modules require Param Module) + Tables + + Forms + Client side image maps + Server side image maps + Ruby + + + + This import brings in the XML namespace attributes The XML attributes + are used by various modules. + + + + + + Document Model module for the XHTML+RDFa Document Type. This schema + file defines all named models used by XHTML Modularization Framework for XHTML+RDFa + Document Type + + + + + Schema that includes all modules (and redefinitions) for XHTML1.1 + Document Type. + + + + + + + + + + + + + + + Redefinition by Client Side Image Map Module + + + + + + + Redefinition by XHTML Event Attribute Module + + + + + + + Target Module - A Attribute Additions + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-rdfa-2.xsd b/resources/schema/xml/xhtml-1.1/xhtml-rdfa-2.xsd new file mode 100644 index 000000000..6eb57eac2 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-rdfa-2.xsd @@ -0,0 +1,124 @@ + + + + This is the XML Schema driver for XHTML + RDFa Please use this namespace + for XHTML elements: "http://www.w3.org/1999/xhtml" $Id: xhtml-rdfa-1.xsd,v 1.2 + 2008/07/02 13:26:46 ahby Exp $ + + + + This is the Schema Driver file for XHTML + RDFa Document Type This schema + + imports external schemas (xml.xsd) + refedines (and include)s schema modules for + XHTML1.1 Document Type. + includes Schema for Named content model for the XHTML1.1 + Document Type XHTML1.1 Document Type includes the following Modules XHTML Core modules + (Required for XHTML Family Conformance) + text + hypertext + lists + structure Other + XHTML modules + Edit + Bdo + Presentational + Link + Meta + Base + Scripting + Style + + Image + Applet + Object + Param (Applet/Object modules require Param Module) + Tables + + Forms + Client side image maps + Server side image maps + Ruby + + + + This import brings in the XML namespace attributes The XML attributes + are used by various modules. + + + + + + Document Model module for the XHTML+RDFa Document Type. This schema + file defines all named models used by XHTML Modularization Framework for XHTML+RDFa + Document Type + + + + + Schema that includes all modules (and redefinitions) for XHTML1.1 + Document Type. + + + + + + + + + + + + + + + Redefinition by Client Side Image Map Module + + + + + + + Redefinition by XHTML Event Attribute Module + + + + + + + Target Module - A Attribute Additions + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-rdfa-model-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-rdfa-model-1.xsd new file mode 100644 index 000000000..cb5160a43 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-rdfa-model-1.xsd @@ -0,0 +1,733 @@ + + + + + + This is the XML Schema module of common content models for XHTML11 + + $Id: xhtml-rdfa-model-1.xsd,v 1.5 2008/07/05 04:30:45 smccarro Exp $ + + + + + + XHTML Document Model + This module describes the groupings of elements/attributes + that make up common content models for XHTML elements. + XHTML has following basic content models: + xhtml.Inline.mix; character-level elements + xhtml.Block.mix; block-like elements, e.g., paragraphs and lists + xhtml.Flow.mix; any block or inline elements + xhtml.HeadOpts.mix; Head Elements + xhtml.InlinePre.mix; Special class for pre content model + xhtml.InlineNoAnchor.mix; Content model for Anchor + + Any groups declared in this module may be used to create + element content models, but the above are considered 'global' + (insofar as that term applies here). XHTML has the + following Attribute Groups + xhtml.Core.extra.attrib + xhtml.I18n.extra.attrib + xhtml.Common.extra + + The above attribute Groups are considered Global + + + + + + XHTML Metainformation Modules + + Attributes defined here: + XHTML RDFa attribtues + + + + + + + Extended I18n attribute + + + + + "dir" Attribute from Bi Directional Text (bdo) Module + + + + + + + Extended Common Attributes + + + + + "style" attribute from Inline Style Module + + + + + + + Attributes from Events Module + + + + + + + Attributes from Metainformation Module + + + + + + + Extend Core Attributes + + + + + Extended Global Core Attributes + + + + + Extended Global I18n attributes + + + + + Extended Global Common Attributes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-rdfa-model-2.xsd b/resources/schema/xml/xhtml-1.1/xhtml-rdfa-model-2.xsd new file mode 100644 index 000000000..770e3c635 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-rdfa-model-2.xsd @@ -0,0 +1,733 @@ + + + + + + This is the XML Schema module of common content models for XHTML11 + + $Id: xhtml-rdfa-model-2.xsd,v 1.4 2015/11/24 13:09:55 smccarro Exp $ + + + + + + XHTML Document Model + This module describes the groupings of elements/attributes + that make up common content models for XHTML elements. + XHTML has following basic content models: + xhtml.Inline.mix; character-level elements + xhtml.Block.mix; block-like elements, e.g., paragraphs and lists + xhtml.Flow.mix; any block or inline elements + xhtml.HeadOpts.mix; Head Elements + xhtml.InlinePre.mix; Special class for pre content model + xhtml.InlineNoAnchor.mix; Content model for Anchor + + Any groups declared in this module may be used to create + element content models, but the above are considered 'global' + (insofar as that term applies here). XHTML has the + following Attribute Groups + xhtml.Core.extra.attrib + xhtml.I18n.extra.attrib + xhtml.Common.extra + + The above attribute Groups are considered Global + + + + + + XHTML Metainformation Modules + + Attributes defined here: + XHTML RDFa attribtues + + + + + + + Extended I18n attribute + + + + + "dir" Attribute from Bi Directional Text (bdo) Module + + + + + + + Extended Common Attributes + + + + + "style" attribute from Inline Style Module + + + + + + + Attributes from Events Module + + + + + + + Attributes from Metainformation Module + + + + + + + Extend Core Attributes + + + + + Extended Global Core Attributes + + + + + Extended Global I18n attributes + + + + + Extended Global Common Attributes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-rdfa-modules-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-rdfa-modules-1.xsd new file mode 100644 index 000000000..eb3931b50 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-rdfa-modules-1.xsd @@ -0,0 +1,552 @@ + + + + + + + This schema includes all modules for XHTML1.1 Document Type. + $Id: xhtml-rdfa-modules-1.xsd,v 1.9 2008/07/05 04:15:37 smccarro Exp $ + + + + + + This schema includes all modules (and redefinitions) + for XHTML1.1 Document Type. + XHTML1.1 Document Type includes the following Modules + + XHTML Core modules (Required for XHTML Family Conformance) + + text + + hypertext + + lists + + structure + + Other XHTML modules + + Edit + + Bdo + + Presentational + + Link + + Meta + + Base + + Scripting + + Style + + Image + + Applet + + Object + + Param (Applet/Object modules require Param Module) + + Tables + + Target + + Forms + + Client side image maps + + Server side image maps + + + + + + + Schema Framework Component Modules: + + notations + + datatypes + + common attributes + + character entities + + + + + + + + Text module + + The Text module includes declarations for all core + text container elements and their attributes. + + + block phrasal + + block structural + + inline phrasal + + inline structural + + Elements defined here: + * address, blockquote, pre, h1, h2, h3, h4, h5, h6 + * div, p + * abbr, acronym, cite, code, dfn, em, kbd, q, samp, strong, var + * br, span + + + + + + + + + Lists module + + Elements defined here: + * dt, dd, dl, ol, ul, li + + + + + + + + Structural module + + Elements defined here: + * title, head, body, html + + + + + + + Redefinition by the XHTML11 Markup (for value of version attr) + + + + + + + + + Original Body Attlist + + + + + + + Redefinition by XHTML Event Attribute Module + + + + + + + + + + + + + + + + + + + + + Edit module + + Elements defined here: + * ins, del + + + + + + + + Bidirectional element module + + Elements defined here: + * bdo + + + + + + + + Presentational module + + Elements defined here: + * hr, b, big, i, small,sub, sup, tt + + + + + + + + Base module + + Elements defined here: + * base + + + + + + + Changes to XHTML base Attlist + + + + + + Original Base Attributes (declared in Base Module) + + + + + + + XHTML Target Module - Attribute additions + + + + + + + + + Scripting module + + Elements defined here: + * script, noscript + + + + + + + + Style module + + Elements defined here: + * style + + + + + + + + Style attribute module + + Attribute defined here: + * style + + + + + + + + Image module + + Elements defined here: + * img + + + + + + + + Original Image Attributes (in Image Module) + + + + + + + Redefinition by Client Side Image Map Module + + + + + + + Redefinition by Server Side Image Module + + + + + + + + + Client-side mage maps module + + Elements defined here: + * area, map + + + + + + + + Original Area Attributes (in CSI Module) + + + + + + + Redefinition by Events Attribute Module + + + + + + + Target Module - Area Attribute Additions + + + + + + + + + Server-side image maps module + + Attributes defined here: + * ismap on img + + + + + + + + Object module + + Elements defined here: + * object + + + + + + + + Original Object Attlist + + + + + + + Redefinition by Client Image Map Module + + + + + + + + + Param module + + Elements defined here: + * param + + + + + + + Tables module + + Elements defined here: + * table, caption, thead, tfoot, tbody, colgroup, col, tr, th, td + + + + + + + + Forms module + + Elements defined here: + * form, label, input, select, optgroup, option, + * textarea, fieldset, legend, button + + + + + + + Changes to XHTML Form Attlist + + + + + + Original Form Attributes (declared in Forms Module) + + + + + + + XHTML Events Module - Attribute additions + + + + + + + XHTML Target Module - Attribute additions + + + + + + + + Changes to XHTML Form Input Element + + + + + + Original Input Attributes (in Forms Module) + + + + + + + Redefinition by Client Side Image Map Module + + + + + + + Redefinition by Server Side Image Map Module + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + Original Label Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + Original Select Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + Original TextArea Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + Original Button Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + Ruby module + + Elements defined here: + * ruby, rbc, rtc, rb, rt, rp + + Note that either Ruby or Basic Ruby should be used but not both + + + + + + + + XHTML Events Modules + + Attributes defined here: + XHTML Event Types + + + + + + + + XHTML Metainformation Modules + + Attributes defined here: + XHTML RDFa attribtues + + + + + + + + XHTML Target Attribute Module + + Attributes defined here: + target + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-rdfa-modules-2.xsd b/resources/schema/xml/xhtml-1.1/xhtml-rdfa-modules-2.xsd new file mode 100644 index 000000000..272e2291e --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-rdfa-modules-2.xsd @@ -0,0 +1,556 @@ + + + + + + + This schema includes all modules for XHTML1.1 Document Type. + $Id: xhtml-rdfa-modules-2.xsd,v 1.4 2015/11/24 13:10:17 smccarro Exp $ + + + + + + This schema includes all modules (and redefinitions) + for XHTML1.1 Document Type. + XHTML1.1 Document Type includes the following Modules + + XHTML Core modules (Required for XHTML Family Conformance) + + text + + hypertext + + lists + + structure + + Other XHTML modules + + Edit + + Bdo + + Presentational + + Link + + Meta + + Base + + Scripting + + Style + + Image + + Applet + + Object + + Param (Applet/Object modules require Param Module) + + Tables + + Target + + Forms + + Client side image maps + + Server side image maps + + + + + + + Schema Framework Component Modules: + + notations + + datatypes + + common attributes + + character entities + + + + + + + + Text module + + The Text module includes declarations for all core + text container elements and their attributes. + + + block phrasal + + block structural + + inline phrasal + + inline structural + + Elements defined here: + * address, blockquote, pre, h1, h2, h3, h4, h5, h6 + * div, p + * abbr, acronym, cite, code, dfn, em, kbd, q, samp, strong, var + * br, span + + + + + + + + Lists module + + Elements defined here: + * dt, dd, dl, ol, ul, li + + + + + + + + Structural module + + Elements defined here: + * title, head, body, html + + + + + + + Redefinition by the XHTML RDFa 1.1 Markup (for value of version attr) + + + + + + + + + + + + + + Original Body Attlist + + + + + + + Redefinition by XHTML Event Attribute Module + + + + + + + + + + + + + + + + + + + + + Edit module + + Elements defined here: + * ins, del + + + + + + + + Bidirectional element module + + Elements defined here: + * bdo + + + + + + + + Presentational module + + Elements defined here: + * hr, b, big, i, small,sub, sup, tt + + + + + + + + Base module + + Elements defined here: + * base + + + + + + + Changes to XHTML base Attlist + + + + + + Original Base Attributes (declared in Base Module) + + + + + + + XHTML Target Module - Attribute additions + + + + + + + + + Scripting module + + Elements defined here: + * script, noscript + + + + + + + + Style module + + Elements defined here: + * style + + + + + + + + Style attribute module + + Attribute defined here: + * style + + + + + + + + Image module + + Elements defined here: + * img + + + + + + + + Original Image Attributes (in Image Module) + + + + + + + Redefinition by Client Side Image Map Module + + + + + + + Redefinition by Server Side Image Module + + + + + + + + + Client-side mage maps module + + Elements defined here: + * area, map + + + + + + + + Original Area Attributes (in CSI Module) + + + + + + + Redefinition by Events Attribute Module + + + + + + + Target Module - Area Attribute Additions + + + + + + + + + Server-side image maps module + + Attributes defined here: + * ismap on img + + + + + + + + Object module + + Elements defined here: + * object + + + + + + + + Original Object Attlist + + + + + + + Redefinition by Client Image Map Module + + + + + + + + + Param module + + Elements defined here: + * param + + + + + + + Tables module + + Elements defined here: + * table, caption, thead, tfoot, tbody, colgroup, col, tr, th, td + + + + + + + + Forms module + + Elements defined here: + * form, label, input, select, optgroup, option, + * textarea, fieldset, legend, button + + + + + + + Changes to XHTML Form Attlist + + + + + + Original Form Attributes (declared in Forms Module) + + + + + + + XHTML Events Module - Attribute additions + + + + + + + XHTML Target Module - Attribute additions + + + + + + + + Changes to XHTML Form Input Element + + + + + + Original Input Attributes (in Forms Module) + + + + + + + Redefinition by Client Side Image Map Module + + + + + + + Redefinition by Server Side Image Map Module + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + Original Label Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + Original Select Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + Original TextArea Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + Original Button Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + Ruby module + + Elements defined here: + * ruby, rbc, rtc, rb, rt, rp + + Note that either Ruby or Basic Ruby should be used but not both + + + + + + + + XHTML Events Modules + + Attributes defined here: + XHTML Event Types + + + + + + + + XHTML Metainformation Modules + + Attributes defined here: + XHTML RDFa attribtues + + + + + + + + XHTML Target Attribute Module + + Attributes defined here: + target + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-role-attrib-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-role-attrib-1.xsd new file mode 100644 index 000000000..b8f3cddcd --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-role-attrib-1.xsd @@ -0,0 +1,19 @@ + + + + + + + This is the XML Schema attribute module for XHTML Role + $Id: xhtml-role-attrib-1.xsd,v 1.2 2010/04/20 19:31:48 smccarro Exp $ + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-ruby-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-ruby-1.xsd new file mode 100644 index 000000000..666f81bd2 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-ruby-1.xsd @@ -0,0 +1,170 @@ + + + + + + This is the Ruby module for XHTML + $Id: xhtml-ruby-1.xsd,v 1.7 2010/05/02 17:22:08 ahby Exp $ + + + + + + + "Ruby" are short runs of text alongside the base text, typically + used in East Asian documents to indicate pronunciation or to + provide a short annotation. The full specification for Ruby is here: + + http://www.w3.org/TR/2001/REC-ruby-20010531/ + + This module defines "Ruby " or "complex Ruby" as described + in the specification: + + http://www.w3.org/TR/2001/REC-ruby-20010531/#complex + + Simple or Basic Ruby are defined in a separate module. + + This module declares the elements and their attributes used to + support complex ruby annotation markup. Elements defined here + * ruby, rbc, rtc, rb, rt, rp + + This module expects the document model to define the + following content models + + InlNoRuby.mix + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-ruby-basic-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-ruby-basic-1.xsd new file mode 100644 index 000000000..436a242c5 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-ruby-basic-1.xsd @@ -0,0 +1,89 @@ + + + + + + This is the XML Schema module for Ruby Basic. + $Id: xhtml-ruby-basic-1.xsd,v 1.6 2005/09/26 22:54:53 ahby Exp $ + + + + + + "Ruby" are short runs of text alongside the base text, typically + used in East Asian documents to indicate pronunciation or to + provide a short annotation. The full specification for Ruby is here: + + http://www.w3.org/TR/2001/REC-ruby-20010531/ + + This module defines "Ruby Basic" or "simple Ruby" as described + in the specification: + + http://www.w3.org/TR/ruby/#simple-ruby1 + + This module declares the elements and their attributes used to + support simple ruby annotation markup. Elements defined here are + * ruby, rb, rt, rp + Ruby Basic does not use the rbc or rtc elements. + The content of the ruby element for Ruby Basic + uses the rp element for fallback purposes. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-script-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-script-1.xsd new file mode 100644 index 000000000..bc6742e30 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-script-1.xsd @@ -0,0 +1,71 @@ + + + + + + This is the XML Schema Scripting module for XHTML + $Id: xhtml-script-1.xsd,v 1.5 2006/09/11 08:50:41 ahby Exp $ + + + + + + Scripting + + * script, noscript + + This module declares element types and attributes used to provide + support for executable scripts as well as an alternate content + container where scripts are not supported. + + + + + + + This import brings in the XML namespace attributes + The module itself does not provide the schemaLocation + and expects the driver schema to provide the + actual SchemaLocation. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-ssismap-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-ssismap-1.xsd new file mode 100644 index 000000000..4e120107e --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-ssismap-1.xsd @@ -0,0 +1,43 @@ + + + + + + This is the XML Schema Server-side Image Maps module for XHTML + $Id: xhtml-ssismap-1.xsd,v 1.3 2005/09/26 22:54:53 ahby Exp $ + + + + + + Server-side Image Maps + + This adds the 'ismap' attribute to the img element to + support server-side processing of a user selection. + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-struct-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-struct-1.xsd new file mode 100644 index 000000000..4f85a5fd5 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-struct-1.xsd @@ -0,0 +1,130 @@ + + + + + + This is the XML Schema Document Structure module for XHTML + Document Structure + + * title, head, body, html + + The Structure Module defines the major structural elements and + their attributes. + + $Id: xhtml-struct-1.xsd,v 1.11 2009/09/30 14:13:35 ahby Exp $ + + + + + + + + This import brings in the XML namespace attributes + The module itself does not provide the schemaLocation + and expects the driver schema to provide the + actual SchemaLocation. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-style-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-style-1.xsd new file mode 100644 index 000000000..1b3e7d3b5 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-style-1.xsd @@ -0,0 +1,53 @@ + + + + + + + This is the XML Schema Stylesheets module for XHTML + $Id: xhtml-style-1.xsd,v 1.5 2006/09/11 10:14:57 ahby Exp $ + + + + + + Stylesheets + + * style + + This module declares the style element type and its attributes, + used to embed stylesheet information in the document head element. + + + + + + + This import brings in the XML namespace attributes + The module itself does not provide the schemaLocation + and expects the driver schema to provide the + actual SchemaLocation. + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-table-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-table-1.xsd new file mode 100644 index 000000000..ec76db3ca --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-table-1.xsd @@ -0,0 +1,272 @@ + + + + + + + This is the XML Schema Tables module for XHTML + $Id: xhtml-table-1.xsd,v 1.3 2005/09/26 22:54:53 ahby Exp $ + + + + + + Tables + + * table, caption, thead, tfoot, tbody, colgroup, col, tr, th, td + + This module declares element types and attributes used to provide + table markup similar to HTML 4.0, including features that enable + better accessibility for non-visual user agents. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-target-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-target-1.xsd new file mode 100644 index 000000000..d8f2770d2 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-target-1.xsd @@ -0,0 +1,49 @@ + + + + + + This is the XML Schema Target module for XHTML + $Id: xhtml-target-1.xsd,v 1.3 2007/04/03 18:27:01 ahby Exp $ + + + + + + + Target + + * target + + This module declares the 'target' attribute used for opening windows + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml-text-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml-text-1.xsd new file mode 100644 index 000000000..432bdad7a --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml-text-1.xsd @@ -0,0 +1,67 @@ + + + + + + Textual Content + This is the XML Schema Text module for XHTML + + The Text module includes declarations for all core + text container elements and their attributes. + + + block phrasal + + block structural + + inline phrasal + + inline structural + + $Id: xhtml-text-1.xsd,v 1.2 2005/09/26 22:54:53 ahby Exp $ + + + + + + + + Block Phrasal module + Elements defined here: + + * address, blockquote, pre, h1, h2, h3, h4, h5, h6 + + + + + + + Block Structural module + Elements defined here: + + * div, p + + + + + + + Inline Phrasal module + Elements defined here: + + * abbr, acronym, cite, code, dfn, em, kbd, q, samp, strong, var + + + + + + + Inline Structural module + Elements defined here: + + * br,span + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml11-model-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml11-model-1.xsd new file mode 100644 index 000000000..1cd4fddde --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml11-model-1.xsd @@ -0,0 +1,716 @@ + + + + + + This is the XML Schema module of common content models for XHTML11 + + $Id: xhtml11-model-1.xsd,v 1.9 2009/02/03 15:14:49 ahby Exp $ + + + + + + XHTML Document Model + This module describes the groupings of elements/attributes + that make up common content models for XHTML elements. + XHTML has following basic content models: + xhtml.Inline.mix; character-level elements + xhtml.Block.mix; block-like elements, e.g., paragraphs and lists + xhtml.Flow.mix; any block or inline elements + xhtml.HeadOpts.mix; Head Elements + xhtml.InlinePre.mix; Special class for pre content model + xhtml.InlineNoAnchor.mix; Content model for Anchor + + Any groups declared in this module may be used to create + element content models, but the above are considered 'global' + (insofar as that term applies here). XHTML has the + following Attribute Groups + xhtml.Core.extra.attrib + xhtml.I18n.extra.attrib + xhtml.Common.extra + + The above attribute Groups are considered Global + + + + + Extended I18n attribute + + + + + "dir" Attribute from Bi Directional Text (bdo) Module + + + + + + + + Extended Common Attributes + + + + + "style" attribute from Inline Style Module + + + + + + + Attributes from Events Module + + + + + + + Extend Core Attributes + + + + + Extended Global Core Attributes + + + + + Extended Global I18n attributes + + + + + Extended Global Common Attributes + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml11-module-redefines-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml11-module-redefines-1.xsd new file mode 100644 index 000000000..808464414 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml11-module-redefines-1.xsd @@ -0,0 +1,335 @@ + + + + + + This XML Schema declares changes to the content models + of modules included in XHTML11 + $Id: xhtml11-module-redefines-1.xsd,v 1.1 2003/09/23 21:12:52 speruvem Exp $ + + + + + + + Module Content Model Redefinitions + + This schema describes the changes (Redefinitions) to + content model of individual modules as they are instantiated as part of + XHTML11 document type + + + + + + + + + + + Redefinition by Base module + + + + + + + + + + + + + + + + + + + + + + + + Redefinition by the XHTML11 Markup (for value of version attr) + + + + + + + + + + Original Body Attlist + + + + + + + Redefinition by XHTML Event Attribute Module + + + + + + + + + + + + + + + Redefinition by Client Side Image Map Module + + + + + + + Redefinition by XHTML Event Attribute Module + + + + + + + + + + + + + + Changes to XHTML Form Attlist + + + + + + Original Form Attributes (declared in Forms Module) + + + + + + + XHTML Events Module - Attribute additions + + + + + + + + + Changes to XHTML Form Input Element + + + + + + Original Input Attributes (in Forms Module) + + + + + + + + Redefinition by Client Side Image Map Module + + + + + + + + Redefinition by Server Side Image Map Module + + + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + + + Original Label Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + + Original Select Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + + Original TextArea Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + + Original Button Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + + + + + + + Original Area Attributes (in CSI Module) + + + + + + + Redefinition by Events Attribute Module + + + + + + + + + + + + + + Original Image Attributes (in Image Module) + + + + + + + Redefinition by Client Side Image Map Module + + + + + + + Redefinition by Server Side Image Module + + + + + + + + + + + + + + Original Link Attributes + + + + + + + + + + + + + Original Base Attributes + + + + + + + + + + + + + Original Object Attlist + + + + + + + Redefinition by Client Image Map Module + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml11-modules-1.xsd b/resources/schema/xml/xhtml-1.1/xhtml11-modules-1.xsd new file mode 100644 index 000000000..e2cce0e9e --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml11-modules-1.xsd @@ -0,0 +1,605 @@ + + + + + + + This schema includes all modules for XHTML1.1 Document Type. + $Id: xhtml11-modules-1.xsd,v 1.10 2009/02/03 15:14:49 ahby Exp $ + + + + + + This schema includes all modules (and redefinitions) + for XHTML1.1 Document Type. + XHTML1.1 Document Type includes the following Modules + + XHTML Core modules (Required for XHTML Family Conformance) + + text + + hypertext + + lists + + structure + + Other XHTML modules + + Edit + + Bdo + + Presentational + + Link + + Meta + + Base + + Scripting + + Style + + Image + + Applet + + Object + + Param (Applet/Object modules require Param Module) + + Tables + + Target + + Forms + + Client side image maps + + Server side image maps + + + + + + + Schema Framework Component Modules: + + notations + + datatypes + + common attributes + + character entities + + + + + + + + Text module + + The Text module includes declarations for all core + text container elements and their attributes. + + + block phrasal + + block structural + + inline phrasal + + inline structural + + Elements defined here: + * address, blockquote, pre, h1, h2, h3, h4, h5, h6 + * div, p + * abbr, acronym, cite, code, dfn, em, kbd, q, samp, strong, var + * br, span + + + + + + + + Hypertext module + + Elements defined here: + * a + + + + + + + + + Redefinition by Client Side Image Map Module + + + + + + + Redefinition by XHTML Event Attribute Module + + + + + + + Target Module - A Attribute Additions + + + + + + + + + Lists module + + Elements defined here: + * dt, dd, dl, ol, ul, li + + + + + + + + Structural module + + Elements defined here: + * title, head, body, html + + + + + + + Redefinition by the XHTML11 Markup (for value of version attr) + + + + + + + + + Original Body Attlist + + + + + + + Redefinition by XHTML Event Attribute Module + + + + + + + + + Edit module + + Elements defined here: + * ins, del + + + + + + + + Bidirectional element module + + Elements defined here: + * bdo + + + + + + + + Presentational module + + Elements defined here: + * hr, b, big, i, small,sub, sup, tt + + + + + + + + Link module + + Elements defined here: + * link + + + + + + + Changes to XHTML Link Attlist + + + + + + Original Link Attributes (declared in Link Module) + + + + + + + XHTML Target Module - Attribute additions + + + + + + + + + Meta module + + Elements defined here: + * meta + + + + + + + + Base module + + Elements defined here: + * base + + + + + + + Changes to XHTML base Attlist + + + + + + Original Base Attributes (declared in Base Module) + + + + + + + XHTML Target Module - Attribute additions + + + + + + + + + Scripting module + + Elements defined here: + * script, noscript + + + + + + + + Style module + + Elements defined here: + * style + + + + + + + + Style attribute module + + Attribute defined here: + * style + + + + + + + + Image module + + Elements defined here: + * img + + + + + + + + Original Image Attributes (in Image Module) + + + + + + + Redefinition by Client Side Image Map Module + + + + + + + Redefinition by Server Side Image Module + + + + + + + + + Client-side mage maps module + + Elements defined here: + * area, map + + + + + + + + Original Area Attributes (in CSI Module) + + + + + + + Redefinition by Events Attribute Module + + + + + + + Target Module - Area Attribute Additions + + + + + + + + + Server-side image maps module + + Attributes defined here: + * ismap on img + + + + + + + + Object module + + Elements defined here: + * object + + + + + + + + Original Object Attlist + + + + + + + Redefinition by Client Image Map Module + + + + + + + + + Param module + + Elements defined here: + * param + + + + + + + Tables module + + Elements defined here: + * table, caption, thead, tfoot, tbody, colgroup, col, tr, th, td + + + + + + + + Forms module + + Elements defined here: + * form, label, input, select, optgroup, option, + * textarea, fieldset, legend, button + + + + + + + Changes to XHTML Form Attlist + + + + + + Original Form Attributes (declared in Forms Module) + + + + + + + XHTML Events Module - Attribute additions + + + + + + + XHTML Target Module - Attribute additions + + + + + + + + Changes to XHTML Form Input Element + + + + + + Original Input Attributes (in Forms Module) + + + + + + + Redefinition by Client Side Image Map Module + + + + + + + Redefinition by Server Side Image Map Module + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + Original Label Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + Original Select Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + Original TextArea Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + Original Button Attributes (in Forms Module) + + + + + + + Redefinition by Event Attribute Module + + + + + + + + + Ruby module + + Elements defined here: + * ruby, rbc, rtc, rb, rt, rp + + Note that either Ruby or Basic Ruby should be used but not both + + + + + + + + XHTML Events Modules + + Attributes defined here: + XHTML Event Types + + + + + + + + XHTML Target Attribute Module + + Attributes defined here: + target + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml11.xsd b/resources/schema/xml/xhtml-1.1/xhtml11.xsd new file mode 100644 index 000000000..262acbf65 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml11.xsd @@ -0,0 +1,104 @@ + + + + + This is the XML Schema driver for XHTML 1.1. + Please use this namespace for XHTML elements: + + "http://www.w3.org/1999/xhtml" + + $Id: xhtml11.xsd,v 1.7 2009/02/03 15:14:49 ahby Exp $ + + + + + + This is XHTML, a reformulation of HTML as a modular XML application + The Extensible HyperText Markup Language (XHTML) + Copyright ©1998-2007 World Wide Web Consortium + (Massachusetts Institute of Technology, European Research Consortium + for Informatics and Mathematics, Keio University). + All Rights Reserved. + + Permission to use, copy, modify and distribute the XHTML Schema + modules and their accompanying xs:documentation for any purpose + and without fee is hereby granted in perpetuity, provided that the above + copyright notice and this paragraph appear in all copies. + The copyright holders make no representation about the suitability of + these XML Schema modules for any purpose. + + They are provided "as is" without expressed or implied warranty. + + + + + This is the Schema Driver file for XHTML1.1 + Document Type + + This schema + + imports external schemas (xml.xsd) + + refedines (and include)s schema modules for XHTML1.1 Document Type. + + includes Schema for Named content model for the + XHTML1.1 Document Type + + XHTML1.1 Document Type includes the following Modules + XHTML Core modules (Required for XHTML Family Conformance) + + text + + hypertext + + lists + + structure + Other XHTML modules + + Edit + + Bdo + + Presentational + + Link + + Meta + + Base + + Scripting + + Style + + Image + + Applet + + Object + + Param (Applet/Object modules require Param Module) + + Tables + + Forms + + Client side image maps + + Server side image maps + + Ruby + + + + + + This import brings in the XML namespace attributes + The XML attributes are used by various modules. + + + + + + + Document Model module for the XHTML1.1 Document Type. + This schema file defines all named models used by XHTML + Modularization Framework for XHTML1.1 Document Type + + + + + + + Schema that includes all modules (and redefinitions) + for XHTML1.1 Document Type. + + + + diff --git a/resources/schema/xml/xhtml-1.1/xhtml2.xsd b/resources/schema/xml/xhtml-1.1/xhtml2.xsd new file mode 100644 index 000000000..cc376a026 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xhtml2.xsd @@ -0,0 +1,21 @@ + + + + + A minimal XML Schema for XHTML 2.0 + $Id: xhtml2.xsd,v 1.4 2005/06/14 15:28:27 mimasa Exp $ + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xml-events-1.xsd b/resources/schema/xml/xhtml-1.1/xml-events-1.xsd new file mode 100644 index 000000000..0d53b8a52 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xml-events-1.xsd @@ -0,0 +1,73 @@ + + + + + + This is the XML Schema for XML Events + + URI: http://www.w3.org/MarkUp/SCHEMA/xml-events-1.xsd + $Id: xml-events-1.xsd,v 1.8 2004/11/22 17:09:15 ahby Exp $ + + + + + + + XML Events element listener + + This module defines the listener element for XML Events. + This element can be used to define event listeners. This + module relies upon the XmlEvents.attlist attribute group + defined in xml-events-attribs-1.xsd. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xml-events-2.xsd b/resources/schema/xml/xhtml-1.1/xml-events-2.xsd new file mode 100644 index 000000000..8df280a24 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xml-events-2.xsd @@ -0,0 +1,73 @@ + + + + + + This is the XML Schema for XML Events + + URI: http://www.w3.org/MarkUp/SCHEMA/xml-events-2.xsd + $Id: xml-events-2.xsd,v 1.2 2008/06/25 14:36:17 smccarro Exp $ + + + + + + + XML Events element listener + + This module defines the listener element for XML Events. + This element can be used to define event listeners. This + module relies upon the XmlEvents.attlist attribute group + defined in xml-events-attribs-2.xsd. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xml-events-attribs-1.xsd b/resources/schema/xml/xhtml-1.1/xml-events-attribs-1.xsd new file mode 100644 index 000000000..ef99128e9 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xml-events-attribs-1.xsd @@ -0,0 +1,73 @@ + + + + + + This is the XML Schema for XML Events global attributes + + URI: http://www.w3.org/MarkUp/SCHEMA/xml-events-attribs-1.xsd + $Id: xml-events-attribs-1.xsd,v 1.7 2004/11/22 17:09:15 ahby Exp $ + + + + + + + XML Event Attributes + + These "global" event attributes are defined in "Attaching + Attributes Directly to the Observer Element" of the XML + Events specification. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xml-events-attribs-2.xsd b/resources/schema/xml/xhtml-1.1/xml-events-attribs-2.xsd new file mode 100644 index 000000000..4f83aaeb1 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xml-events-attribs-2.xsd @@ -0,0 +1,75 @@ + + + + + + This is the XML Schema for XML Events global attributes + + URI: http://www.w3.org/MarkUp/SCHEMA/xml-events-attribs-2.xsd + $Id: xml-events-attribs-2.xsd,v 1.2 2008/06/25 14:36:21 smccarro Exp $ + + + + + + + XML Event Attributes + + These "global" event attributes are defined in "Attaching + Attributes Directly to the Observer Element" of the XML + Events specification. + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xml-events-copyright-1.xsd b/resources/schema/xml/xhtml-1.1/xml-events-copyright-1.xsd new file mode 100644 index 000000000..ebe0e9240 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xml-events-copyright-1.xsd @@ -0,0 +1,34 @@ + + + + + + This is XML Events, a generalized event model for XML-based + markup languages. + + Copyright 2001-2003 World Wide Web Consortium + (Massachusetts Institute of Technology, European Research + Consortium for Informatics and Mathematics, Keio University). + All Rights Reserved. + + Permission to use, copy, modify and distribute the + XML Events Schema modules and their accompanying xs:documentation + for any purpose and without fee is hereby granted in perpetuity, + provided that the above copyright notice and this paragraph appear + in all copies. + + The copyright holders make no representation about the suitability of + these XML Schema modules for any purpose. + + They are provided "as is" without expressed or implied warranty. + + + + diff --git a/resources/schema/xml/xhtml-1.1/xml-events-copyright-2.xsd b/resources/schema/xml/xhtml-1.1/xml-events-copyright-2.xsd new file mode 100644 index 000000000..6a1f5b248 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xml-events-copyright-2.xsd @@ -0,0 +1,34 @@ + + + + + + This is XML Events, a generalized event model for XML-based + markup languages. + + Copyright 2001-2007 World Wide Web Consortium + (Massachusetts Institute of Technology, European Research + Consortium for Informatics and Mathematics, Keio University). + All Rights Reserved. + + Permission to use, copy, modify and distribute the + XML Events Schema modules and their accompanying xs:documentation + for any purpose and without fee is hereby granted in perpetuity, + provided that the above copyright notice and this paragraph appear + in all copies. + + The copyright holders make no representation about the suitability of + these XML Schema modules for any purpose. + + They are provided "as is" without expressed or implied warranty. + + + + diff --git a/resources/schema/xml/xhtml-1.1/xml-handlers-1.xsd b/resources/schema/xml/xhtml-1.1/xml-handlers-1.xsd new file mode 100644 index 000000000..36fbd8a80 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xml-handlers-1.xsd @@ -0,0 +1,136 @@ + + + + + + This is the XML Schema for XML Handlers + + URI: http://www.w3.org/MarkUp/SCHEMA/xml-handlers-1.xsd + $Id: xml-handlers-1.xsd,v 1.1 2008/06/25 14:36:29 smccarro Exp $ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xml-handlers-2.xsd b/resources/schema/xml/xhtml-1.1/xml-handlers-2.xsd new file mode 100644 index 000000000..3c307c6b7 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xml-handlers-2.xsd @@ -0,0 +1,98 @@ + + + + + + This is the XML Schema for XML Events + + URI: http://www.w3.org/MarkUp/SCHEMA/xml-handlers-2.xsd + $Id: xml-handlers-2.xsd,v 1.1 2007/02/15 23:03:14 jean-gui Exp $ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xml-script-1.xsd b/resources/schema/xml/xhtml-1.1/xml-script-1.xsd new file mode 100644 index 000000000..5315d455d --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xml-script-1.xsd @@ -0,0 +1,38 @@ + + + + + + This is the XML Schema for XML Scripting + + URI: http://www.w3.org/MarkUp/SCHEMA/xml-script-1.xsd + $Id: xml-script-1.xsd,v 1.1 2008/06/25 14:36:34 smccarro Exp $ + + + + + + + + + + + + + + + + + + diff --git a/resources/schema/xml/xhtml-1.1/xml.xsd b/resources/schema/xml/xhtml-1.1/xml.xsd new file mode 100644 index 000000000..70f125ae5 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xml.xsd @@ -0,0 +1,286 @@ + + + + + + +
+

About the XML namespace

+ +
+

+ This schema document describes the XML namespace, in a form + suitable for import by other schema documents. +

+

+ See + http://www.w3.org/XML/1998/namespace.html and + + http://www.w3.org/TR/REC-xml for information + about this namespace. +

+

+ Note that local names in this namespace are intended to be + defined only by the World Wide Web Consortium or its subgroups. + The names currently defined in this namespace are listed below. + They should not be used with conflicting semantics by any Working + Group, specification, or document instance. +

+

+ See further below in this document for more information about how to refer to this schema document from your own + XSD schema documents and about the + namespace-versioning policy governing this schema document. +

+
+
+
+
+ + + + +
+ +

lang (as an attribute name)

+

+ denotes an attribute whose value + is a language code for the natural language of the content of + any element; its value is inherited. This name is reserved + by virtue of its definition in the XML specification.

+ +
+
+

Notes

+

+ Attempting to install the relevant ISO 2- and 3-letter + codes as the enumerated possible values is probably never + going to be a realistic possibility. +

+

+ See BCP 47 at + http://www.rfc-editor.org/rfc/bcp/bcp47.txt + and the IANA language subtag registry at + + http://www.iana.org/assignments/language-subtag-registry + for further information. +

+

+ The union allows for the 'un-declaration' of xml:lang with + the empty string. +

+
+
+
+ + + + + + + + + +
+ + + + +
+ +

space (as an attribute name)

+

+ denotes an attribute whose + value is a keyword indicating what whitespace processing + discipline is intended for the content of the element; its + value is inherited. This name is reserved by virtue of its + definition in the XML specification.

+ +
+
+
+ + + + + + +
+ + + +
+ +

base (as an attribute name)

+

+ denotes an attribute whose value + provides a URI to be used as the base for interpreting any + relative URIs in the scope of the element on which it + appears; its value is inherited. This name is reserved + by virtue of its definition in the XML Base specification.

+ +

+ See http://www.w3.org/TR/xmlbase/ + for information about this attribute. +

+
+
+
+
+ + + + +
+ +

id (as an attribute name)

+

+ denotes an attribute whose value + should be interpreted as if declared to be of type ID. + This name is reserved by virtue of its definition in the + xml:id specification.

+ +

+ See http://www.w3.org/TR/xml-id/ + for information about this attribute. +

+
+
+
+
+ + + + + + + + + + +
+ +

Father (in any context at all)

+ +
+

+ denotes Jon Bosak, the chair of + the original XML Working Group. This name is reserved by + the following decision of the W3C XML Plenary and + XML Coordination groups: +

+
+

+ In appreciation for his vision, leadership and + dedication the W3C XML Plenary on this 10th day of + February, 2000, reserves for Jon Bosak in perpetuity + the XML name "xml:Father". +

+
+
+
+
+
+ + + +
+

About this schema document

+ +
+

+ This schema defines attributes and an attribute group suitable + for use by schemas wishing to allow xml:base, + xml:lang, xml:space or + xml:id attributes on elements they define. +

+

+ To enable this, such a schema must import this schema for + the XML namespace, e.g. as follows: +

+
+          <schema . . .>
+           . . .
+           <import namespace="http://www.w3.org/XML/1998/namespace"
+                      schemaLocation="http://www.w3.org/2001/xml.xsd"/>
+     
+

+ or +

+
+           <import namespace="http://www.w3.org/XML/1998/namespace"
+                      schemaLocation="xml_2009_01.xsd"/>
+     
+

+ Subsequently, qualified reference to any of the attributes or the + group defined below will have the desired effect, e.g. +

+
+          <type . . .>
+           . . .
+           <attributeGroup ref="xml:specialAttrs"/>
+     
+

+ will define a type which will schema-validate an instance element + with any of those attributes. +

+
+
+
+
+ + + +
+

Versioning policy for this schema document

+
+

+ In keeping with the XML Schema WG's standard versioning + policy, this schema document will persist at + + http://www.w3.org/2009/01/xml.xsd. +

+

+ At the date of issue it can also be found at + + http://www.w3.org/2001/xml.xsd. +

+

+ The schema document at that URI may however change in the future, + in order to remain compatible with the latest version of XML + Schema itself, or with the XML namespace itself. In other words, + if the XML Schema or XML namespaces change, the version of this + document at + http://www.w3.org/2001/xml.xsd + + will change accordingly; the version at + + http://www.w3.org/2009/01/xml.xsd + + will not change. +

+

+ Previous dated (and unchanging) versions of this schema + document are at: +

+ +
+
+
+
+ +
diff --git a/resources/schema/xml/xhtml-1.1/xml_2009_01.xsd b/resources/schema/xml/xhtml-1.1/xml_2009_01.xsd new file mode 100644 index 000000000..588f14d60 --- /dev/null +++ b/resources/schema/xml/xhtml-1.1/xml_2009_01.xsd @@ -0,0 +1,286 @@ + + + + + + +
+

About the XML namespace

+ +
+

+ This schema document describes the XML namespace, in a form + suitable for import by other schema documents. +

+

+ See + http://www.w3.org/XML/1998/namespace.html and + + http://www.w3.org/TR/REC-xml for information + about this namespace. +

+

+ Note that local names in this namespace are intended to be + defined only by the World Wide Web Consortium or its subgroups. + The names currently defined in this namespace are listed below. + They should not be used with conflicting semantics by any Working + Group, specification, or document instance. +

+

+ See further below in this document for more information about how to refer to this schema document from your own + XSD schema documents and about the + namespace-versioning policy governing this schema document. +

+
+
+
+
+ + + + +
+ +

lang (as an attribute name)

+

+ denotes an attribute whose value + is a language code for the natural language of the content of + any element; its value is inherited. This name is reserved + by virtue of its definition in the XML specification.

+ +
+
+

Notes

+

+ Attempting to install the relevant ISO 2- and 3-letter + codes as the enumerated possible values is probably never + going to be a realistic possibility. +

+

+ See BCP 47 at + http://www.rfc-editor.org/rfc/bcp/bcp47.txt + and the IANA language subtag registry at + + http://www.iana.org/assignments/language-subtag-registry + for further information. +

+

+ The union allows for the 'un-declaration' of xml:lang with + the empty string. +

+
+
+
+ + + + + + + + + +
+ + + + +
+ +

space (as an attribute name)

+

+ denotes an attribute whose + value is a keyword indicating what whitespace processing + discipline is intended for the content of the element; its + value is inherited. This name is reserved by virtue of its + definition in the XML specification.

+ +
+
+
+ + + + + + +
+ + + +
+ +

base (as an attribute name)

+

+ denotes an attribute whose value + provides a URI to be used as the base for interpreting any + relative URIs in the scope of the element on which it + appears; its value is inherited. This name is reserved + by virtue of its definition in the XML Base specification.

+ +

+ See http://www.w3.org/TR/xmlbase/ + for information about this attribute. +

+
+
+
+
+ + + + +
+ +

id (as an attribute name)

+

+ denotes an attribute whose value + should be interpreted as if declared to be of type ID. + This name is reserved by virtue of its definition in the + xml:id specification.

+ +

+ See http://www.w3.org/TR/xml-id/ + for information about this attribute. +

+
+
+
+
+ + + + + + + + + + +
+ +

Father (in any context at all)

+ +
+

+ denotes Jon Bosak, the chair of + the original XML Working Group. This name is reserved by + the following decision of the W3C XML Plenary and + XML Coordination groups: +

+
+

+ In appreciation for his vision, leadership and + dedication the W3C XML Plenary on this 10th day of + February, 2000, reserves for Jon Bosak in perpetuity + the XML name "xml:Father". +

+
+
+
+
+
+ + + +
+

About this schema document

+ +
+

+ This schema defines attributes and an attribute group suitable + for use by schemas wishing to allow xml:base, + xml:lang, xml:space or + xml:id attributes on elements they define. +

+

+ To enable this, such a schema must import this schema for + the XML namespace, e.g. as follows: +

+
+          <schema . . .>
+           . . .
+           <import namespace="http://www.w3.org/XML/1998/namespace"
+                      schemaLocation="http://www.w3.org/2001/xml.xsd"/>
+     
+

+ or +

+
+           <import namespace="http://www.w3.org/XML/1998/namespace"
+                      schemaLocation="xml_2009_01.xsd"/>
+     
+

+ Subsequently, qualified reference to any of the attributes or the + group defined below will have the desired effect, e.g. +

+
+          <type . . .>
+           . . .
+           <attributeGroup ref="xml:specialAttrs"/>
+     
+

+ will define a type which will schema-validate an instance element + with any of those attributes. +

+
+
+
+
+ + + +
+

Versioning policy for this schema document

+
+

+ In keeping with the XML Schema WG's standard versioning + policy, this schema document will persist at + + http://www.w3.org/2009/01/xml.xsd. +

+

+ At the date of issue it can also be found at + + http://www.w3.org/2001/xml.xsd. +

+

+ The schema document at that URI may however change in the future, + in order to remain compatible with the latest version of XML + Schema itself, or with the XML namespace itself. In other words, + if the XML Schema or XML namespaces change, the version of this + document at + http://www.w3.org/2001/xml.xsd + + will change accordingly; the version at + + http://www.w3.org/2009/01/xml.xsd + + will not change. +

+

+ Previous dated (and unchanging) versions of this schema + document are at: +

+ +
+
+
+
+ +
diff --git a/tests/QARegressionTests/test_Issues/test_CoreIssue897.py b/tests/QARegressionTests/test_Issues/test_CoreIssue897.py new file mode 100644 index 000000000..c21c68041 --- /dev/null +++ b/tests/QARegressionTests/test_Issues/test_CoreIssue897.py @@ -0,0 +1,158 @@ +import os +import subprocess +import unittest +import openpyxl +import pytest +from conftest import get_python_executable +from QARegressionTests.globals import ( + issue_datails_sheet, + rules_report_sheet, + issue_sheet_record_column, + issue_sheet_variable_column, + issue_sheet_values_column, +) + + +@pytest.mark.regression +class TestGetXHTMLErrors(unittest.TestCase): + def test_positive_dataset(self): + # Run the command in the terminal + command = [ + f"{get_python_executable()}", + "-m", + "core", + "validate", + "-s", + "usdm", + "-v", + "4-0", + "-dp", + os.path.join( + "tests", + "resources", + "CoreIssue897", + "Positive_datasets.json", + ), + "-lr", + os.path.join("tests", "resources", "CoreIssue897", "Rule.yml"), + ] + subprocess.run(command, check=True) + + # Get the latest created Excel file + files = os.listdir() + excel_files = [ + file + for file in files + if file.startswith("CORE-Report-") and file.endswith(".xlsx") + ] + excel_file_path = sorted(excel_files)[-1] + # # Open the Excel file + workbook = openpyxl.load_workbook(excel_file_path) + + # Go to the "Issue Details" sheet + sheet = workbook[issue_datails_sheet] + + record_column = sheet[issue_sheet_record_column] + variables_column = sheet[issue_sheet_variable_column] + values_column = sheet[issue_sheet_values_column] + + record_values = [cell.value for cell in record_column[1:]] + variables_values = [cell.value for cell in variables_column[1:]] + values_column_values = [cell.value for cell in values_column[1:]] + + # Remove None values using list comprehension + record_values = [value for value in record_values if value is not None] + variables_values = [value for value in variables_values if value is not None] + values_column_values = [ + value for value in values_column_values if value is not None + ] + rules_values = [ + row for row in workbook[rules_report_sheet].iter_rows(values_only=True) + ][1:] + rules_values = [row for row in rules_values if any(row)] + # Perform the assertion + # Ensure only two negative values are caught + assert rules_values[0][0] == "CORE-000409" + assert rules_values[0][-1] == "SUCCESS" + assert len(record_values) == 0 + assert len(variables_values) == 0 + assert len(values_column_values) == 0 + if os.path.exists(excel_file_path): + os.remove(excel_file_path) + + def test_negaive_dataset(self): + # Run the command in the terminal + command = [ + f"{get_python_executable()}", + "-m", + "core", + "validate", + "-s", + "usdm", + "-v", + "4-0", + "-dp", + os.path.join( + "tests", + "resources", + "CoreIssue897", + "Negative_datasets.json", + ), + "-lr", + os.path.join("tests", "resources", "CoreIssue897", "Rule.yml"), + ] + subprocess.run(command, check=True) + + # Get the latest created Excel file + files = os.listdir() + excel_files = [ + file + for file in files + if file.startswith("CORE-Report-") and file.endswith(".xlsx") + ] + excel_file_path = sorted(excel_files)[-1] + # Open the Excel file + workbook = openpyxl.load_workbook(excel_file_path) + + # --- Dataset Details --- + dataset_sheet = workbook["Dataset Details"] + dataset_values = [row for row in dataset_sheet.iter_rows(values_only=True)][1:] + dataset_values = [row for row in dataset_values if any(row)] + assert len(dataset_values) > 0 + assert dataset_values[0][0] == "NarrativeContentItem.xpt" + assert dataset_values[0][-1] == 170 + + # --- Issue Summary --- + issue_summary_sheet = workbook["Issue Summary"] + summary_values = [ + row for row in issue_summary_sheet.iter_rows(values_only=True) + ][1:] + summary_values = [row for row in summary_values if any(row)] + assert len(summary_values) > 0 + assert summary_values[0][1] == "CORE-000409" + assert summary_values[0][3] == 4 + + # --- Issue Details --- + issue_details_sheet = workbook["Issue Details"] + details_values = [ + row for row in issue_details_sheet.iter_rows(values_only=True) + ][1:] + details_values = [row for row in details_values if any(row)] + assert all(row[0] == "CORE-000409" for row in details_values) + assert len(details_values) == 4 + + # --- Rules Report --- + rules_values = [ + row for row in workbook["Rules Report"].iter_rows(values_only=True) + ][1:] + rules_values = [row for row in rules_values if any(row)] + assert len(rules_values) > 0 + assert rules_values[0][0] == "CORE-000409" + assert rules_values[0][-1] == "SUCCESS" + + if os.path.exists(excel_file_path): + os.remove(excel_file_path) + + +# if __name__ == "__main__": +# unittest.main() diff --git a/tests/resources/CoreIssue897/Negative_datasets.json b/tests/resources/CoreIssue897/Negative_datasets.json new file mode 100644 index 000000000..c47c5e54d --- /dev/null +++ b/tests/resources/CoreIssue897/Negative_datasets.json @@ -0,0 +1,1439 @@ +{ + "datasets": [ + { + "filename": "NarrativeContentItem.xpt", + "name": "NarrativeContentItem", + "label": "Narrative Content Item", + "domain": "NARRATIVECONTENTITEM", + "variables": [ + { + "name": "parent_entity", + "label": "Parent Entity Name", + "type": "String", + "length": null + }, + { + "name": "parent_id", + "label": "Parent Entity Id", + "type": "String", + "length": null + }, + { + "name": "parent_rel", + "label": "Name of Relationship from Parent Entity", + "type": "String", + "length": null + }, + { + "name": "rel_type", + "label": "Type of Relationship", + "type": "String", + "length": null + }, + { + "name": "id", + "label": "(Narrative Content Item Id)", + "type": "String", + "length": null + }, + { + "name": "name", + "label": "Narrative Content Item Name", + "type": "String", + "length": null + }, + { + "name": "text", + "label": "Narrative Content Item Text", + "type": "String", + "length": null + }, + { + "name": "instanceType", + "label": "(Narrative Content Item Instance Type)", + "type": "String", + "length": null + } + ], + "records": { + "parent_entity": [ + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent" + ], + "parent_id": [ + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "NarrativeContent_1", + "NarrativeContent_2", + "NarrativeContent_3", + "NarrativeContent_4", + "NarrativeContent_5", + "NarrativeContent_6", + "NarrativeContent_7", + "NarrativeContent_8", + "NarrativeContent_9", + "NarrativeContent_10", + "NarrativeContent_11", + "NarrativeContent_12", + "NarrativeContent_13", + "NarrativeContent_14", + "NarrativeContent_15", + "NarrativeContent_16", + "NarrativeContent_17", + "NarrativeContent_18", + "NarrativeContent_19", + "NarrativeContent_20", + "NarrativeContent_21", + "NarrativeContent_22", + "NarrativeContent_23", + "NarrativeContent_24", + "NarrativeContent_25", + "NarrativeContent_26", + "NarrativeContent_27", + "NarrativeContent_28", + "NarrativeContent_29", + "NarrativeContent_30", + "NarrativeContent_31", + "NarrativeContent_32", + "NarrativeContent_33", + "NarrativeContent_34", + "NarrativeContent_35", + "NarrativeContent_36", + "NarrativeContent_37", + "NarrativeContent_38", + "NarrativeContent_39", + "NarrativeContent_40", + "NarrativeContent_41", + "NarrativeContent_42", + "NarrativeContent_43", + "NarrativeContent_44", + "NarrativeContent_45", + "NarrativeContent_46", + "NarrativeContent_47", + "NarrativeContent_48", + "NarrativeContent_49", + "NarrativeContent_50", + "NarrativeContent_51", + "NarrativeContent_52", + "NarrativeContent_53", + "NarrativeContent_54", + "NarrativeContent_55", + "NarrativeContent_56", + "NarrativeContent_57", + "NarrativeContent_58", + "NarrativeContent_59", + "NarrativeContent_60", + "NarrativeContent_61", + "NarrativeContent_62", + "NarrativeContent_63", + "NarrativeContent_64", + "NarrativeContent_65", + "NarrativeContent_66", + "NarrativeContent_67", + "NarrativeContent_68", + "NarrativeContent_69", + "NarrativeContent_70", + "NarrativeContent_71", + "NarrativeContent_72", + "NarrativeContent_73", + "NarrativeContent_74", + "NarrativeContent_75", + "NarrativeContent_76", + "NarrativeContent_77", + "NarrativeContent_81", + "NarrativeContent_82", + "NarrativeContent_83", + "NarrativeContent_91", + "NarrativeContent_93", + "NarrativeContent_96", + "NarrativeContent_111", + "NarrativeContent_112" + ], + "parent_rel": [ + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId" + ], + "rel_type": [ + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference" + ], + "id": [ + "NarrativeContentItem_1", + "NarrativeContentItem_2", + "NarrativeContentItem_3", + "NarrativeContentItem_4", + "NarrativeContentItem_5", + "NarrativeContentItem_6", + "NarrativeContentItem_7", + "NarrativeContentItem_8", + "NarrativeContentItem_9", + "NarrativeContentItem_10", + "NarrativeContentItem_11", + "NarrativeContentItem_12", + "NarrativeContentItem_13", + "NarrativeContentItem_14", + "NarrativeContentItem_15", + "NarrativeContentItem_16", + "NarrativeContentItem_17", + "NarrativeContentItem_18", + "NarrativeContentItem_19", + "NarrativeContentItem_20", + "NarrativeContentItem_21", + "NarrativeContentItem_22", + "NarrativeContentItem_23", + "NarrativeContentItem_24", + "NarrativeContentItem_25", + "NarrativeContentItem_26", + "NarrativeContentItem_27", + "NarrativeContentItem_28", + "NarrativeContentItem_29", + "NarrativeContentItem_30", + "NarrativeContentItem_31", + "NarrativeContentItem_32", + "NarrativeContentItem_33", + "NarrativeContentItem_34", + "NarrativeContentItem_35", + "NarrativeContentItem_36", + "NarrativeContentItem_37", + "NarrativeContentItem_38", + "NarrativeContentItem_39", + "NarrativeContentItem_40", + "NarrativeContentItem_41", + "NarrativeContentItem_42", + "NarrativeContentItem_43", + "NarrativeContentItem_44", + "NarrativeContentItem_45", + "NarrativeContentItem_46", + "NarrativeContentItem_47", + "NarrativeContentItem_48", + "NarrativeContentItem_49", + "NarrativeContentItem_50", + "NarrativeContentItem_51", + "NarrativeContentItem_52", + "NarrativeContentItem_53", + "NarrativeContentItem_54", + "NarrativeContentItem_55", + "NarrativeContentItem_56", + "NarrativeContentItem_57", + "NarrativeContentItem_58", + "NarrativeContentItem_59", + "NarrativeContentItem_60", + "NarrativeContentItem_61", + "NarrativeContentItem_62", + "NarrativeContentItem_63", + "NarrativeContentItem_64", + "NarrativeContentItem_65", + "NarrativeContentItem_66", + "NarrativeContentItem_67", + "NarrativeContentItem_68", + "NarrativeContentItem_69", + "NarrativeContentItem_70", + "NarrativeContentItem_71", + "NarrativeContentItem_72", + "NarrativeContentItem_73", + "NarrativeContentItem_74", + "NarrativeContentItem_75", + "NarrativeContentItem_76", + "NarrativeContentItem_77", + "NarrativeContentItem_78", + "NarrativeContentItem_79", + "NarrativeContentItem_80", + "NarrativeContentItem_81", + "NarrativeContentItem_82", + "NarrativeContentItem_83", + "NarrativeContentItem_84", + "NarrativeContentItem_85", + "NarrativeContentItem_1", + "NarrativeContentItem_2", + "NarrativeContentItem_3", + "NarrativeContentItem_4", + "NarrativeContentItem_5", + "NarrativeContentItem_6", + "NarrativeContentItem_7", + "NarrativeContentItem_8", + "NarrativeContentItem_9", + "NarrativeContentItem_10", + "NarrativeContentItem_11", + "NarrativeContentItem_12", + "NarrativeContentItem_13", + "NarrativeContentItem_14", + "NarrativeContentItem_15", + "NarrativeContentItem_16", + "NarrativeContentItem_17", + "NarrativeContentItem_18", + "NarrativeContentItem_19", + "NarrativeContentItem_20", + "NarrativeContentItem_21", + "NarrativeContentItem_22", + "NarrativeContentItem_23", + "NarrativeContentItem_24", + "NarrativeContentItem_25", + "NarrativeContentItem_26", + "NarrativeContentItem_27", + "NarrativeContentItem_28", + "NarrativeContentItem_29", + "NarrativeContentItem_30", + "NarrativeContentItem_31", + "NarrativeContentItem_32", + "NarrativeContentItem_33", + "NarrativeContentItem_34", + "NarrativeContentItem_35", + "NarrativeContentItem_36", + "NarrativeContentItem_37", + "NarrativeContentItem_38", + "NarrativeContentItem_39", + "NarrativeContentItem_40", + "NarrativeContentItem_41", + "NarrativeContentItem_42", + "NarrativeContentItem_43", + "NarrativeContentItem_44", + "NarrativeContentItem_45", + "NarrativeContentItem_46", + "NarrativeContentItem_47", + "NarrativeContentItem_48", + "NarrativeContentItem_49", + "NarrativeContentItem_50", + "NarrativeContentItem_51", + "NarrativeContentItem_52", + "NarrativeContentItem_53", + "NarrativeContentItem_54", + "NarrativeContentItem_55", + "NarrativeContentItem_56", + "NarrativeContentItem_57", + "NarrativeContentItem_58", + "NarrativeContentItem_59", + "NarrativeContentItem_60", + "NarrativeContentItem_61", + "NarrativeContentItem_62", + "NarrativeContentItem_63", + "NarrativeContentItem_64", + "NarrativeContentItem_65", + "NarrativeContentItem_66", + "NarrativeContentItem_67", + "NarrativeContentItem_68", + "NarrativeContentItem_69", + "NarrativeContentItem_70", + "NarrativeContentItem_71", + "NarrativeContentItem_72", + "NarrativeContentItem_73", + "NarrativeContentItem_74", + "NarrativeContentItem_75", + "NarrativeContentItem_76", + "NarrativeContentItem_77", + "NarrativeContentItem_78", + "NarrativeContentItem_79", + "NarrativeContentItem_80", + "NarrativeContentItem_81", + "NarrativeContentItem_82", + "NarrativeContentItem_83", + "NarrativeContentItem_84", + "NarrativeContentItem_85" + ], + "name": [ + "NCI_1", + "NCI_2", + "NCI_3", + "NCI_4", + "NCI_5", + "NCI_6", + "NCI_7", + "NCI_8", + "NCI_9", + "NCI_10", + "NCI_11", + "NCI_12", + "NCI_13", + "NCI_14", + "NCI_15", + "NCI_16", + "NCI_17", + "NCI_18", + "NCI_19", + "NCI_20", + "NCI_21", + "NCI_22", + "NCI_23", + "NCI_24", + "NCI_25", + "NCI_26", + "NCI_27", + "NCI_28", + "NCI_29", + "NCI_30", + "NCI_31", + "NCI_32", + "NCI_33", + "NCI_34", + "NCI_35", + "NCI_36", + "NCI_37", + "NCI_38", + "NCI_39", + "NCI_40", + "NCI_41", + "NCI_42", + "NCI_43", + "NCI_44", + "NCI_45", + "NCI_46", + "NCI_47", + "NCI_48", + "NCI_49", + "NCI_50", + "NCI_51", + "NCI_52", + "NCI_53", + "NCI_54", + "NCI_55", + "NCI_56", + "NCI_57", + "NCI_58", + "NCI_59", + "NCI_60", + "NCI_61", + "NCI_62", + "NCI_63", + "NCI_64", + "NCI_65", + "NCI_66", + "NCI_67", + "NCI_68", + "NCI_69", + "NCI_70", + "NCI_71", + "NCI_72", + "NCI_73", + "NCI_74", + "NCI_75", + "NCI_76", + "NCI_77", + "NCI_78", + "NCI_79", + "NCI_80", + "NCI_81", + "NCI_82", + "NCI_83", + "NCI_84", + "NCI_85", + "NCI_1", + "NCI_2", + "NCI_3", + "NCI_4", + "NCI_5", + "NCI_6", + "NCI_7", + "NCI_8", + "NCI_9", + "NCI_10", + "NCI_11", + "NCI_12", + "NCI_13", + "NCI_14", + "NCI_15", + "NCI_16", + "NCI_17", + "NCI_18", + "NCI_19", + "NCI_20", + "NCI_21", + "NCI_22", + "NCI_23", + "NCI_24", + "NCI_25", + "NCI_26", + "NCI_27", + "NCI_28", + "NCI_29", + "NCI_30", + "NCI_31", + "NCI_32", + "NCI_33", + "NCI_34", + "NCI_35", + "NCI_36", + "NCI_37", + "NCI_38", + "NCI_39", + "NCI_40", + "NCI_41", + "NCI_42", + "NCI_43", + "NCI_44", + "NCI_45", + "NCI_46", + "NCI_47", + "NCI_48", + "NCI_49", + "NCI_50", + "NCI_51", + "NCI_52", + "NCI_53", + "NCI_54", + "NCI_55", + "NCI_56", + "NCI_57", + "NCI_58", + "NCI_59", + "NCI_60", + "NCI_61", + "NCI_62", + "NCI_63", + "NCI_64", + "NCI_65", + "NCI_66", + "NCI_67", + "NCI_68", + "NCI_69", + "NCI_70", + "NCI_71", + "NCI_72", + "NCI_73", + "NCI_74", + "NCI_75", + "NCI_76", + "NCI_77", + "NCI_78", + "NCI_79", + "NCI_80", + "NCI_81", + "NCI_82", + "NCI_83", + "NCI_84", + "NCI_85" + ], + "text": [ + "
\r\n
\r\n
\r\n

The information contained in this clinical study protocol is

Copyright © 2006 Eli Lilly and Company.

\r\n
\r\n
\r\n
\r\n
\r\n

\r\n
\r\n
\r\n
\r\n
\r\n

\r\n
\r\n
\r\n
\r\n
\r\n

\r\n
\r\n
\r\n
", + "

The M1 muscarinic-cholinergic receptor is 1 of 5 characterized muscarinic-cholinergic receptor subtypes (Fisher and Barak 1994). M1 receptors in the cerebral cortex and hippocampus are, for the most part, preserved in Alzheimer's disease (AD), while the presynaptic neurons projecting to these receptors from the nucleus basalis of Meynert degenerate (Bierer et al. 1995). The presynaptic loss of cholinergic neurons has been correlated to the antimortum cognitive impairment in AD patients, prompting speculation that replacement therapy with cholinomimetics will alleviate the cognitive dysfunction of the disorder (Fisher and Barak 1994).

\r\n

Xanomeline is a novel M1 agonist which has shown high affinity for the M1 receptor subtype (in transfected cells), and substantially less or no affinity for other muscarinic subtypes. Positron emission tomography (PET) studies of 11C-labeled xanomeline in cynomolgus monkeys have suggested that the compound crosses the blood-brain barrier and preferentially binds the striatum and neocortex.

\r\n

Clinical development of an oral formulation of xanomeline for the indication of mild and moderate AD was initiated approximately 4 years ago. A large-scale study of safety and efficacy provided evidence that an oral dosing regimen of 75 mg three times daily (TID) may be associated with enhanced cognition and improved clinical global impression, relative to placebo. As well, a dramatic reduction in psychosis, agitation, and other problematic behaviors, which often complicate the course of the disease, was documented. However, the discontinuation rate associated with this oral dosing regimen was 58.6%, and alternative clinical strategies have been sought to improve tolerance for the compound.

\r\n

To that end, development of a Transdermal Therapeutic System (TTS) has been initiated. Relative to the oral formulation, the transdermal formulation eliminates high concentrations of xanomeline in the gastrointestinal (GI) tract and presystemic (firstpass) metabolism. Three transdermal delivery systems, hereafter referred to as the xanomeline TTS Formulation A, xanomeline TTS Formulation B, and xanomeline TTS formulation E have been manufactured by Lohman Therapy Systems GmbH of Andernach Germany. TTS Formulation A is 27 mg xanomeline freebase in a 25-cm2 matrix. TTS Formulation B is 57.6 mg xanomeline freebase in a 40-cm2 matrix. Formulation E has been produced in 2 patch sizes: 1) 54 mg xanomeline freebase with 0.06 mg Vitamin E USP in a 50-cm2 matrix and 2) 27 mg xanomeline freebase with 0.03 mg Vitamin E USP in a 25-cm2 matrix. For a detailed description of the composition of these formulations please refer to Part II, Section 14 of the Xanomeline (LY246708) Clinical Investigator's Brochure. For characterization of the safety, tolerance, and pharmacokinetics of xanomeline TTS Formulations A, B, and E, please refer to Part II, Sections 7, 8, and 10 of the Xanomeline (LY246708) Clinical Investigator's Brochure. Formulation E will be studied in this protocol, H2Q-MC-LZZT(c).

", + "
", + "

The primary objectives of this study are

\r\n
", + "

The secondary objectives of this study are

\r\n
", + "
", + "

Patients with probable mild to moderate AD will be studied in a randomized, double-blind, parallel (3 arm), placebo-controlled trial of 26 weeks duration. The study will be conducted on an outpatient basis. Approximately 300 patients will be enrolled (see Schedule of Events for Protocol H2Q-MC-LZZT(c), Attachment LZZT.1).

\r\n

Following informed consent, patients will be screened at Visit 1. At screening, patients will undergo complete neuropsychiatric assessment, psychometric testing, and general medical assessment (including medical history, pre-existing conditions, physical examination). In addition, vital signs, temperature, medication history, electrocardiogram (ECG), chest x-ray, and safety laboratories will be obtained. During the screening visit, patients will wear a placebo TTS to determine willingness and ability to comply with transdermal administration procedures. If patients have not had central nervous system (CNS) imaging in the previous 12 months, a computed tomography (CT) or magnetic resonance imaging (MRI) scan will be obtained. If patients are insulin dependent diabetics, a hemoglobin A 1c will be obtained. Screening exams and procedures may be performed after Visit 1; however, their results must be completed and available prior to randomization. The screening process should occur within 2 weeks of randomization (Visit 3 of the study).

\r\n

Patients who meet enrollment criteria from Visit 1 will proceed to Visit 2 at which time they will undergo a 24-hour Ambulatory ECG. At Visit 3 the Ambulatory ECG will be removed and patients will be randomized to 1 of 3 treatment arms. The treatment arms will include a placebo arm, a low-dose xanomeline arm (50 cm 2 TTS Formulation E, 54 mg xanomeline), and a high-dose xanomeline arm (75 cm 2 TTS Formulation E, 81 mg xanomeline). All patients receiving xanomeline will be started at 50 cm 2 TTS Formulation E. For the first 8 weeks of treatment, patients will be assessed at clinic visits every 2 weeks and, thereafter, at clinic visits every 4 weeks. Patients who discontinue prior to Visit 12 (Week 24) will be brought back for full efficacy assessments at or near to 24 weeks, whenever possible.

\r\n

A Data Safety Monitoring Board (DSMB), chaired by an external cardiologist, will meet after 75, 150, 225, and 300 patients have completed 1 month of treatment. The DSMB will review cardiovascular findings to decide if discontinuation of the study or any treatment arm is appropriate, if additional cardiovascular monitoring is required, if further cardiovascular monitoring is unnecessary, or if adjustment of dose within a treatment arm (or arms) is appropriate (see Section 3.9.4).

\r\n

At Visits 3, 8, 10, and 12, efficacy instruments (ADAS-Cog, CIBIC+, and DAD) will be administered. NPI-X will be administered at 2-week intervals either at clinic visits or via a telephone interview. Vital signs, temperature, and an assessment of adverse events will

\r\n

be obtained at all clinic visits. An electrocardiogram (ECG), and chemistry/hematology safety labs will be obtained at Visits 4, 5, 7, 8, 9, 10, 11, 12, and 13. Urinalysis will be done at Visits 4, 9, and 12. Use of concomitant medications will be collected at Visits 3, 4, 5, 7, 8, 9, 10, 11, 12, and 13. Plasma levels of xanomeline and metabolites will be obtained at Visits 3, 4, 5, 7, 9, and 11. At Visits 3, 4, 5, 7, 8, 9, 10, 11, and 12, medications will be dispensed to the patients.

\r\n

Visits 1 through 13 should be scheduled relative to Visit 3 (Week 0 - randomization). Visits 4, 5, 7, 8, and 13 should occur within 3 days of their scheduled date. Visits 9, 10, 11, and 12 should occur within 4 days of their scheduled date. At Visit 13 patients will be given the option to enter the open-label extension phase (see Section 3.10.3. Study Extensions).

\r\n\"Alt\r\n

Figure LZZT.1. Illustration of study design for Protocol H2Q-MC-LZZT(c).

", + "

Previous studies of the oral formulation have shown that xanomeline tartrate may improve behavior and cognition. Effects on behavior are manifest within 2 to 4 weeks of initiation of treatment. The same studies have shown that 8 to 12 weeks are required to demonstrate effects on cognition and clinical global assessment. This study is intended to determine the acute and chronic effects of the TTS formulation in AD; for that reason, the study is of 26 weeks duration. Dosage specification has been made on the basis of tolerance to the xanomeline TTS in a clinical pharmacology study (H2Q-EW-LKAA), and target plasma levels as determined in studies of the oral formulation of xanomeline (H2Q-MC-LZZA).

\r\n

The parallel dosing regimen maximizes the ability to make direct comparisons between the treatment groups. The use of placebo allows for a blinded, thus minimally biased, study. The placebo treatment group is a comparator group for efficacy and safety assessment.

\r\n

Two interim analyses are planned for this study. The first interim analysis will occur when 50% of the patients have completed Visit 8 (8 weeks). If required, the second interim analysis will occur when 50% of the patients have completed Visit 12 (24 weeks). (See Section 4.6, Interim Analyses.)

", + "

The name, title, and institution of the investigator(s) is/are listed on the Investigator/Contacts cover pages provided with this protocol. If the investigator is changed after the study has been approved by an ethical review board, or a regulatory agency, or by Lilly, this addition will not be considered a change to the protocol. However, the Investigator/Contacts cover pages will be updated to provide this information.

", + "

The final report coordinating investigator will sign the final clinical study report for this study, indicating agreement with the analyses, results, and conclusions of the report.

\r\n

The investigator who will serve as the final report coordinating investigator will be an individual that is involved with the design and analysis of the study. This final report coordinating investigator will be named by the sponsor of the study.

", + "
", + "

An Ethical Review Board (ERB) approved informed consent will be signed by the patient (and/or legal representative) and caregiver after the nature of the study is explained.

", + "

For Lilly studies, the following definitions are used:

\r\n
\r\n
Screen
\r\n
\r\n

Screening is the act of determining if an individual meets minimum requirements to become part of a pool of potential candidates for participation in a clinical study.

\r\n

In this study, screening will include asking the candidate preliminary questions (such as age and general health status) and conducting invasive or diagnostic procedures and/or tests (for example, diagnostic psychological tests, x-rays, blood draws). Patients will sign the consent at their screening visit, thereby consenting to undergo the screening procedures and to participate in the study if they qualify.

\r\n
\r\n
\r\n
\r\n
To enter
\r\n
\r\n

Patients entered into the study are those from whom informed consent for the study has been obtained. Adverse events will be reported for each patient who has entered the study, even if the patient is never assigned to a treatment group (enrolled).

\r\n
\r\n
\r\n
\r\n
To enroll
\r\n
\r\n

Patients who are enrolled in the study are those who have been assigned to a treatment group. Patients who are entered into the study but fail to meet criteria specified in the protocol for treatment assignment will not be enrolled in the study.

\r\n
\r\n
\r\n

At Visit 1, patients who meet the enrollment criteria of Mini-Mental State Examination (MMSE) score of 10 to 23 (Attachment LZZT.6), Hachinski Ischemia Score ≤4 (Attachment LZZT.8), a physical exam, safety labs, ECG, and urinalysis, will proceed to Visit 2 and Visit 3. At Visit 3, patients whose CNS imaging and other pending labs from Visit 1 satisfy the inclusion criteria (Section 3.4.2.1) will be enrolled in the study. Approximately 300 patients with a diagnosis of probable mild to moderate AD will be enrolled in the study.

", + "

Patients may be included in the study only if they meet all the following criteria:

\r\n
01
02
03
04
05
06
07
08
", + "

Patients will be excluded from the study for any of the following reasons:

\r\n
09
10
11
12
13
14
15
16b
17
18
19
20
21
22
23
24
25
26
27b
28b
29b
30b
31b
", + "

The criteria for enrollment must be followed explicitly. If there is inadvertent enrollment of individuals who do not meet enrollment criteria, these individuals should be discontinued from the study. Such individuals can remain in the study only if there are ethical reasons to have them continue. In these cases, the investigator must obtain approval from the Lilly research physician for the study participant to continue in the study (even if the study is being conducted through a contract research organization).

", + "

Probable AD will be defined clinically by NINCDS/ADRDA guidelines as follows:

\r\n
", + "

Approximately 100 patients will be randomized to each of the 3 treatment groups. Previous experience with the oral formulation of xanomeline suggests that this sample size has 90% power to detect a 3.0 mean treatment difference in ADAS-Cog (p<.05, two-sided), based on a standard deviation of 6.5. Furthermore, this sample size has 80% power to detect a 0.36 mean treatment difference in CIBIC+ (p<.05, two-sided), based on a standard deviation of 0.9.

", + "

Commencing at Visit 1, all patients will be assigned an identification number. This identification number and the patient's three initials must appear on all patient-related documents submitted to Lilly.

\r\n

When qualified for enrollment at Visit 3 the patient will be randomized to 1 of 3 treatment arms.

", + "
", + "
\r\n\r\n\r\n\r\n\r\n\r\n\r\n

Primary Study Material:

Xanomeline

TTS (adhesive patches)

50 cm 2 , 54 mg* 25 cm 2 , 27 mg*

Comparator Material:

Placebo

TTS

Identical in appearance to primary study material

\r\n

*All doses are measured in terms of the xanomeline base.

\r\n

Patches should be stored at controlled room temperature, and all used patches must be handled and disposed of as biohazardous waste.

\r\n

For a detailed description of the composition of these formulations please refer to Part II, Section 14 of the Xanomeline (LY246708) Clinical Investigator's Brochure.

", + "

To test acute tolerance of transdermal formulation, patients will have a TTS (placebo) administered at the start of Visit 1, and removed at the conclusion of Visit 1. The patient's and caregiver's willingness to comply with 26 weeks of transdermal therapy should be elicited, and those patients/caregivers unwilling to comply should be excluded.

\r\n

Upon enrollment at Visit 3, and on the morning of each subsequent day of therapy , xanomeline or placebo will be administered with the application of 2 adhesive patches, one 50 cm2 in area, the other 25 cm2 in area. Each morning, prior to the application of the patches, hydrocortisone cream (1%) should be applied to the skin at the intended site of administration, rubbed in, and allowed to penetrate for approximately 30 minutes. Thereafter, excess cream should be wiped away and the patches applied.

\r\n

The patches are to be worn continuously throughout the day, for a period of approximately 12 to 14 hours, and removed in the evening. After removal of the patches, hydrocortisone cream (1%) should be applied locally to the site of administration.

\r\n

Patches should be applied to a dry, intact, non-hairy area. Applying the patch to a shaved area is not recommended. The application site of the patches should be rotated according to the following schedule:

\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n

Day

Patch Location

Sunday

right or left upper arm

Monday

right or left upper back

Tuesday

right or left lower back (above belt line)

Wednesday

right or left buttocks

Thursday

right or left mid-axillary region

Friday

right or left upper thigh

Saturday

right or left upper chest

\r\n

Patients and caregivers are free to select either the left or right site within the constraints of the rotation schedule noted above. Patches should be applied at approximately the same time each day. For patients who habitually bathe in the morning, the patient should bathe prior to application of new patches. Every effort should be taken to allow for morning administration of the patches. Exceptions allowing administration of TTS patches at night instead of in the morning will be made on a case-by-case basis by the CRO medical monitor. In the event that some adhesive remains on the patient's skin and cannot be removed with normal bathing, a special solution will be provided to remove the adhesive.

\r\n

Following randomization at Visit 3, patients will be instructed to call the site if they have difficulty with application or wearing of patches. In the event that a patch becomes detached, a new patch of the same size should be applied (at earliest convenience) to an area of the dermis adjacent to the detachment site, and the rotation schedule should be resumed the following morning. If needed, the edges of the patch may be secured with a special adhesive tape that will be provided. If daily doses are reduced, improperly administered, or if a patch becomes detached and requires application of a new patch on three or more days in any 30-day period, the CRO research physician will be notified.

\r\n

If the daily dose is reduced or improperly administered in the 24 hours prior to any scheduled clinic visit, the visit should be rescheduled (except for early termination and retrieval visits).

\r\n

Patients must be instructed to return all used and unused study drug to the investigator at each visit for proper disposal and CT reconciliation by the investigator.

", + "

The study will be double-blind. To further preserve the blinding of the study, only a minimum number of Lilly and CRO personnel will see the randomization table and codes before the study is complete.

\r\n

Emergency codes generated by a computer drug-labeling system will be available to the investigator. These codes, which reveal the patients treatment group, may be opened during the study only if the choice of follow-up treatment depends on the patient's therapy assignment.

\r\n

The investigator should make every effort to contact the clinical research physician prior to unblinding a patient's therapy assignment. If a patient's therapy assignment is unblinded, Lilly must be notified immediately by telephone. After the study, the investigator must return all sealed and any opened codes.

", + "

Intermittent use of chloral hydrate, zolpidem, or lorazepam is permitted during this clinical trial as indicated for agitation or sleep. If medication is required for agitation for a period exceeding 1 week, a review of the patient's status should be made in consultation with the CRO research physician. Caregivers and patients should be reminded that these medications should not be taken within 24 hours of a clinic visit (including the enrollment visit), and administration of efficacy measures should be deferred if the patient has been treated with these medications within the previous 24 hours.

\r\n

If an antihistamine is required during the study, Claritin® (loratadine) or Allegra® (fexofenadine hydrochloride) are the preferred agents, but should not be taken within 24 hours of a clinic visit. Intermittent use (per package insert) of antitussives (containing antihistamines or codeine) and select narcotic analgesics (acetaminophen with oxycodone, acetaminophen with codeine) are permitted during the trial. Caregivers and patients should be reminded that antihistamines and narcotics should not be taken within 3 days of a clinic efficacy visit (including enrollment visit). If an H 2 blocker is required during the study, Axid® (nizatidine) will be permitted on a case-by-case basis by the CRO medical monitor. For prostatic hypertrophy, small doses (2 mg per day) of Hytrin® (terazosin) or Cardura® (doxazosin) will be permitted on a case-by-case basis. Please consult the medical monitor. The calcium channel blockers Cardene® (nicardipine),

\r\n

Norvasc® (amlodipine), and DynaCirc® (isradipine) are allowed during the study. If a patient has been treated with any medication within disallowed time periods prior to the clinic visit, efficacy measures should be deferred.

\r\n

Other classes of medications not stated in Exclusion Criteria, Section 3.4.2.2, will be permitted. Patients who require treatment with an excluded medication (Section 3.4.2.2) will be discontinued from the study following consultation with the CRO research physician.

", + "
", + "

See Schedule of Events, Attachment LZZT.1 for the times of the study at which efficacy data will be collected.

", + "

The following measures will be performed in the course of the study. At Visits 3, 8, 10, and 12, ADAS-Cog, CIBIC+, and DAD will be administered. NPI-X will be administered at 2-week intervals either at clinic visits or via a telephone interview. Efficacy measures will also be collected at early termination visits, and at the retrieval visit. The neuropsychological assessment should be performed first; other protocol requirements, such as labs and the physical, should follow.

\r\n
    \r\n
  1. Alzheimer's Disease Assessment Scale - Cognitive Subscale (ADAS-Cog): ADAS-Cog is an established measure of cognitive function in Alzheimer's Disease. This scale has been incorporated into this study by permission of Dr. Richard C. Mohs and the American Journal of Psychiatry and was adapted from an article entitled, “The Alzheimer's Disease Assessment Scale (ADAS),” which was published in the American Journal of Psychiatry, Volume No.141, pages 1356-1364, November, 1984, Copyright 1984.

    \r\n

    The ADAS-Cog (11) and the ADAS-Cog (14): The ADAS-Cog (11) is a standard 11-item instrument used to assess word recall, naming objects, commands, constructional praxis, ideational praxis, orientation, word recognition tasks, spoken language ability, comprehension, word finding difficulty, and recall of test instructions. For the purposes of this study, three items (delayed word recall, attention/visual search task, and maze solution) have been added to the ADAS-Cog (11) to assess the patient's attention and concentration. The 14 item instrument will be referred to as the ADAS-Cog (14). At each efficacy visit, all 14 items will be assessed, and in subsequent data analyses, performance on the ADAS-Cog (14) and performance on the subset ADAS-Cog (11) will be considered.

  2. \r\n
  3. Video-referenced Clinician's Interview-Based Impression of Change (CIBIC+): The CIBIC+ is an assessment of the global clinical status relative to baseline. The CIBIC+ used in this study is derived from the Clinical Global Impression of Change, an instrument in the public domain, developed by the National Institute on Aging Alzheimer's Disease Study Units Program (1 U01 AG10483; Leon Thal, Principal Investigator). The instrument employs semi-structured interviews with the patient and caregiver, to assess mental/cognitive state, behavior, and function. These domains are not individually scored, but rather are aggregated in the assignment of a global numeric score on a 1 to 7 scale (1 = marked improvement; 4 = no change; and 7 = marked worsening).

    \r\n

    The clinician assessing CIBIC+ will have at least one year of experience with the instrument and will remain blinded to all other efficacy and safety measures.

  4. \r\n
  5. Revised Neuropsychiatric Inventory (NPI-X): The NPI-X is an assessment of change in psychopathology in patients with dementia. The NPI-X is administered to the designated caregiver. This instrument has been revised from its original version (Cummings et al. 1994) and incorporated into this study with the permission of Dr. Jeffrey L. Cummings.

  6. \r\n
  7. Disability Assessment for Dementia (DAD): The DAD is used to assess functional abilities of activities of daily living (ADL) in individuals with cognitive impairment. This scale has been revised and incorporated into this study by permission of Louise Gauthier, M.Sc., and Dr. Isabelle Gelinas. The DAD is administered to the designated caregiver.

  8. \r\n
\r\n

For each instrument, each assessment is to be performed by the same trained health care professional. If circumstances preclude meeting this requirement, the situation is to be documented on the Clinical Report Form (CRF), and the CRO research physician is to be notified.

\r\n

In addition to the efficacy measures noted above, a survey form will be used to collect information from the caregiver on TTS acceptability (Attachment LZZT.9).

", + "

Group mean changes from baseline in the primary efficacy parameters will serve as efficacy criteria. The ADAS-Cog (11) and the video-referenced CIBIC+ will serve as the primary efficacy instruments. Secondary efficacy instruments will include the DAD, the NPI-X, and the ADAS-Cog (14). The procedures and types of analyses to be done are outlined in Section 4.

\r\n

The primary analysis of efficacy will include only the data obtained up to and including the visit of discontinuation of study drug. Furthermore, the primary analysis will not include efficacy data obtained at any visit where the study drug was not administered in the preceding three days. Analyses that include the retrieved dropouts are considered secondary.

", + "

Blood samples (7 mL) for the determination of xanomeline concentrations in plasma will be collected from each patient at Visits 3, 4, 5, 7, 9, and 11. The blood sample drawn at Visit 3 is a baseline sample. The remaining 5 clinic visits should be scheduled so that 1 blood sample is collected at any time during each of the following intervals: early AM visit (hold application of new patch until after blood sample is collected); 9AM to 11AM; 11AM to 1PM; 1PM to 3PM; and 3PM to 5PM. Collection of blood samples during each of these intervals should not occur in any particular order, nor should they occur in the same order for each patient. Every effort should be made to comply with the suggested sampling times. This blood-sampling schedule is based on a sparse sampling strategy where only a few samples will be collected from each patient. The most crucial aspect of the sampling design is to record the date and exact time the sample was drawn and to record the date and time of patch application on the day of the clinic visit and the previous 2 days.

\r\n

If a patient is discontinued from the study prior to protocol completion, a pharmacokinetic blood sample should be drawn at the early discontinuation visit. The date and exact time the sample was drawn and the date of the last patch application should be recorded.

\r\n

Immediately after collection, each sample will be centrifuged at approximately 177 × G for 15 minutes. The plasma will be transferred into a polypropylene tube bearing the identical label as the blood collection tube. Samples will be capped and frozen at approximately −20°C. Care must be taken to insure that the samples remain frozen during transit.

\r\n

The samples will be shipped on dry ice to Central Laboratory.

", + "

Investigators are responsible for monitoring the safety of patients who have entered this study and for alerting CRO to any event that seems unusual, even if this event may be considered an unanticipated benefit to the patient. See Section 3.9.3.2.1.

\r\n

Investigators must ensure that appropriate medical care is maintained throughout the study and after the trial (for example, to follow adverse events).

", + "

Safety measures will be performed at designated times by recording adverse events, laboratory test results, vital signs (including supine/standing pulse and blood pressure readings) ECG monitoring, and Ambulatory ECGs (see Schedule of Events, Attachment LZZT.1).

", + "

Lilly has standards for reporting adverse events that are to be followed, regardless of applicable regulatory requirements that are less stringent. For purposes of collecting and evaluating all information about Lilly drugs used in clinical trials, an adverse event is defined as any undesirable experience or an unanticipated benefit (see Section 3.9.3.2.1) that occurs after informed consent for the study has been obtained, without regard to treatment group assignment, even if no study medication has been taken. Lack of drug effect is not an adverse event in clinical trials, because the purpose of the clinical trial is to establish drug effect.\r\n

At the first visit, study site personnel will question the patient and will note the occurrence and nature of presenting condition(s) and of any preexisting condition(s). At subsequent visits, site personnel will again question the patient and will note any change in the presenting condition(s), any change in the preexisting condition(s), and/or the occurrence and nature of any adverse events.

", + "

All adverse events must be reported to CRO via case report form.

\r\n

Study site personnel must report to CRO immediately, by telephone, any serious adverse event (see Section 3.9.3.2.2 below), or if the investigator unblinds a patient's treatment group assignment because of an adverse event or for any other reason.

\r\n

If a patient's dosage is reduced or if a patient is discontinued from the study because of any significant laboratory abnormality, inadequate response to treatment, or any other reason, the circumstances and data leading to any such dosage reduction or discontinuation must be reported and clearly documented by study site personnel on the clinical report form.

\r\n

An event that may be considered an unanticipated benefit to the patient (for example, sleeping longer) should be reported to CRO as an adverse event on the clinical report form. “Unanticipated benefit” is a COSTART classification term. In cases where the investigator notices an unanticipated benefit to the patient, study site personnel should enter the actual term such as “sleeping longer,” and code “unanticipated benefit” in the clinical report form adverse event section.

\r\n

Solicited adverse events from the skin rash questionnaire (see Section 3.9.3.4) should be reported on the questionnaire only and not also on the adverse event clinical report form

", + "

Study site personnel must report to CRO immediately, by telephone, any adverse event from this study that is alarming or that:

\r\n\r\n

Definition of overdose: For a drug under clinical investigation, an overdose is any intentional or unintentional consumption of the drug (by any route) that exceeds the dose recommended in the Clinical Investigator's Brochure or in an investigational protocol, whichever dose is larger. For a marketed drug, a drug overdose is any intentional or unintentional consumption of the drug (by any route) that exceeds the dose listed in product labeling, even if the larger dose is prescribed by a physician.

", + "

Table LZZT.1 lists the clinical laboratory tests that will be performed at Visit 1.

\r\n

Table LZZT.1. Laboratory Tests Performed at Admission (Visit 1)

\r\n

Safety Laboratory Tests

\r\n\r\n\r\n\r\n\r\n\r\n
\r\n

Hematology:

\r\n
    \r\n
  • Hemoglobin
  • \r\n
  • Hematocrit
  • \r\n
  • Erythrocyte count (RBC)
  • \r\n
  • Mean cell volume (MCV)
  • \r\n
  • Mean cell hemoglobin (MCH)
  • \r\n
  • Mean cell hemoglobin concentration (MCHC)
  • \r\n
  • Leukocytes (WBC)
  • \r\n
  • Neutrophils, segmented
  • \r\n
  • Neutrophils, juvenile (bands)
  • \r\n
  • Lymphocytes
  • \r\n
  • Monocytes
  • \r\n
  • Eosinophils
  • \r\n
  • Basophils
  • \r\n
  • Platelet
  • \r\n
  • Cell morphology
  • \r\n
\r\n

Urinalysis:

\r\n
    \r\n
  • Color
  • \r\n
  • Specific gravity
  • \r\n
  • pH
  • \r\n
  • Protein
  • \r\n
  • Glucose
  • \r\n
  • Ketones
  • \r\n
  • Bilirubin
  • \r\n
  • Urobilinogen
  • \r\n
  • Blood
  • \r\n
  • Nitrite
  • \r\n
  • Microscopic examination of sediment
  • \r\n
\r\n
\r\n

Clinical Chemistry - Serum Concentration of:

\r\n
    \r\n
  • Sodium
  • \r\n
  • Potassium
  • \r\n
  • Bicarbonate
  • \r\n
  • Total bilirubin
  • \r\n
  • Alkaline phosphatase (ALP)
  • \r\n
  • Gamma-glutamyl transferase (GGT)
  • \r\n
  • Alanine transaminase (ALT/SGPT)
  • \r\n
  • Aspartate transaminase (AST/SGOT)
  • \r\n
  • Blood urea nitrogen (BUN)
  • \r\n
  • Serum creatinine
  • \r\n
  • Uric acid
  • \r\n
  • Phosphorus
  • \r\n
  • Calcium
  • \r\n
  • Glucose, nonfasting
  • \r\n
  • Total protein
  • \r\n
  • Albumin
  • \r\n
  • Cholesterol
  • \r\n
  • Creatine kinase (CK)
  • \r\n
\r\n

Thyroid Function Test (Visit 1 only):

\r\n
    \r\n
  • Free thyroid index
  • \r\n
  • T3 Uptake
  • \r\n
  • T4
  • \r\n
  • Thyroid-stimulating hormone (TSH)
  • \r\n
\r\n

Other Tests (Visit 1 only):

\r\n
    \r\n
  • Folate
  • \r\n
  • Vitamin B 12
  • \r\n
  • Syphilis screening
  • \r\n
  • Hemoglobin A1C (IDDM patients only)
\r\n
\r\n

Laboratory values that fall outside a clinically accepted reference range or values that differ significantly from previous values must be evaluated and commented on by the investigator by marking CS (for clinically significant) or NCS (for not clinically significant) next to the values. Any clinically significant laboratory values that are outside a clinically acceptable range or differ importantly from a previous value should be further commented on in the clinical report form comments page.

\r\n

Hematology, and clinical chemistry will also be performed at Visits 4, 5, 7, 8, 9, 10, 11, 12, and 13. Patients that experience a rash and/or eosinophilia may have additional hematology samples obtained as described in 3.9.3.4 (Other Safety Measures).

\r\n

Urinalysis will also be performed at Visits 4, 9, and 12. The following criteria have been developed to monitor hepatic function.

\r\n
", + "
Patients experiencing Rash and/or Eosinophilia\r\n

The administration of placebo and xanomeline TTS is associated with a rash and/or eosinophilia in some patients. The rash is characterized in the following ways:

\r\n\r\n

It does not appear that the rash constitutes a significant safety risk; however, it could affect the well-being of the patients. The following monitoring is specified:

\r\n

Skin Rash Follow-up

\r\n

For patients who exit the study or its extension with rash at the site(s) of application:

\r\n
    \r\n
  1. Approximately 2 weeks after the last visit, the study site personnel should contact the patient/caregiver by phone and complete the skin rash questionnaire. (Note: those patients with rash who have previously exited the study or its extension should be contacted at earliest convenience.)

  2. \r\n
  3. If caregiver states unequivocally that skin problems have completely resolved, no further follow-up is needed.

  4. \r\n
  5. If caregiver reports scarring and/or other problems, patient should return to clinic for a follow-up visit. The skin rash questionnaire should again be completed. If in the opinion of the investigator, further follow-up is required, contact the CRO medical monitor. Completed skin rash questionnaires should be faxed to CRO.

  6. \r\n
\r\n

Completion of the questionnaires will create a separate data set for solicited adverse events. In completing these forms please note the following:

\r\n
    \r\n
  1. Solicited events (events discovered as result of completion of follow-up questionnaires) should be reported on questionnaire page only.

  2. \r\n
  3. Spontaneously reported adverse events (events presented by the patient without direct questioning of the event) should be reported as described in 3.9.3.2 .1 (Adverse Event Reporting Requirements).

  4. \r\n
\r\n

Serious adverse events should be handled and reported as described in 3.9.3.2.1 without regard to whether the event is solicited or spontaneously reported.

\r\n

Eosinophilia Follow-up

\r\n
    \r\n
  1. For patients that are currently in the study with eosinophil counts greater than 0. 6x10 3 /microliter:

    \r\n
    • Repeat hematology at each visit until resolved in the opinion of the investigator.

  2. \r\n
  3. For patients that are currently in the study with eosinophil counts greater than 1.5x10 3 /microliter:

    \r\n
    • Obtain hematology profile every 2 weeks until resolved or explained by other causes in the opinion of the investigator.

    • \r\n
    • Notify CRO medical monitor.

    • \r\n
  4. \r\n
  5. For patients with eosinophil counts greater than 0.6x10 3 /microliter at exit \r\nfrom the study or its extension:

    \r\n
      \r\n
    • Obtain hematology profile approximately every 2 weeks until resolved or, in the opinion of the investigator, explained by other causes. (Note: patients with eosinophil counts greater than 0.6x10 3 /microliter who have previously exited the study or its extension should return for hematology profile at earliest convenience.)

    • \r\n
  6. \r\n
", + "

Patient should lie supine quietly for at least 5 minutes prior to vital signs measurement. Blood pressure should be measured in the dominant arm with a standardized mercury manometer according to the American Heart Association standard recommendations. Diastolic blood pressure will be measured as the point of disappearance of the Korotkoff sounds (phase V). Heart rate will be measured by auscultation. Patient should then stand up. Blood pressure should again be measured in the dominant arm and heart rate should be measured after approximately 1 and 3 minutes.

\r\n

An automated blood pressure cuff may be used in place of a mercury manometer if it is regularly (at least monthly) standardized against a mercury manometer.

", + "

Cardiovascular status will be assessed during the trial with the following measures:

\r\n
", + "

The CRO research physician will monitor safety data throughout the course of the study.

\r\n

Cardiovascular measures, including ECGs and 24-hour Ambulatory ECGs (see Section 3.9.3.4.2) will be monitored on an ongoing basis as follows:

\r\n\r\n

In addition to ongoing monitoring of cardiac measures, a comprehensive, periodic review of cardiovascular safety data will be conducted by the DSMB, which will be chaired by an external cardiologist with expertise in arrhythmias, their pharmacological bases, and their clinical implications. The membership of the board will also include two other external cardiologists, a cardiologist from Lilly, a statistician from Lilly, and the Lilly research physician. Only the three external cardiologists will be voting members.

\r\n

After approximately 75 patients have completed 1 month of treatment, the DSMB will meet to decide:

\r\n\r\n

If necessary, this analysis will be repeated after 150 patients have completed 1 month of treatment, after 225 patients have completed 1 month of treatment, and after 300 patients have completed 1 month of treatment. Primary consideration will be given to the frequency of pauses documented in Ambulatory ECG reports. The number of pauses greater than or equal to 2, 3, 4, 5, and 6 seconds will be tabulated. Primary analysis will focus on the number of pauses greater than or equal to 3 seconds.

\r\n

In the event of a high incidence of patient discontinuation due to syncope, the following guideline may be employed by the DSMB in determining if discontinuation of any treatment arm is appropriate. If the frequency of syncope in a xanomeline treatment arm relative to the frequency of syncope in the placebo arm equals or exceeds the following numbers, then consideration will be given to discontinuing that treatment arm. The Type I error rate for this rule is approximately 0.032 if the incidence in each group is 0.04. The power of this rule is 0.708 if the incidence is 0.04 for placebo and 0.16 for xanomeline TTS.

\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n

Placebo

Xanomeline

PlaceboXanomeline

0

6

615

1

7

716

2

9

817

3

11

918

4

12

1020

5

13

X2X (2-fold)
\r\n

This rule has been used in other studies for monitoring spontaneous events with an incidence of less than 10%. This rule is constructed assuming a 2-group comparison with each group having a final sample size of 100. Unblinding which occurs during these analyses will be at the group level and will be documented.

\r\n

The stopping rule based on Ambulatory ECG findings is as follows:

\r\n

If the number of patients experiencing a pause of ≥6 seconds in a xanomeline treatment arm relative to the number of patients in the placebo arm equals or exceeds the numbers in the following table, then that treatment arm will be discontinued. The Type I error rate for this rule is approximately 0.044 if the incidence in each group is 0.01. The power of this rule is 0.500 if the incidence is 0.01 for placebo and 0.04 for xanomeline TTS.

\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n

Placebo

Xanomeline

0

3

1

5

2

6

3

7

4

8

x

2x

", + "

The medications and efficacy measurements have been used in other studies in elderly subjects and patients.

", + "
", + "

Participation in the study shall be terminated for any patient who is unable or unwilling to comply with the study protocol or who develops a serious adverse event.

\r\n

In addition, patients may be discontinued for any of the following reasons:

\r\n\r\n

If a patient's participation terminates early, an early termination visit should be scheduled. Upon decision to discontinue a patient from the study, the patient's dose should be titrated down by instructing the patient to immediately remove the 25-cm2 patch. Patients should be instructed to continue to apply a 50-cm2 patch daily until the early termination visit, at which time the drug will be discontinued. Physical exam, vital signs, temperature, use of concomitant medications, chemistry/hematology/urinalysis labs, xanomeline plasma sample, TTS acceptability survey, efficacy measures, adverse events, and an ECG will be collected at the early termination visit.

\r\n

In the event that a patient's participation or the study itself is terminated, the patient shall return all study drug(s) to the investigator.

", + "

If possible, patients who have terminated early will be retrieved on the date which would have represented Visit 12 (Week 24). Vital signs, temperature, use of concomitant medications, adverse events, and efficacy measure assessment will be gathered at this visit. If the patient is not retrievable, this will be documented in the source record.

", + "

All patients who are enrolled in the study will be included in the efficacy analysis and the safety analysis. Patients will not be excluded from the efficacy analysis for reasons such as non-compliance or ineligibility, except for the time period immediately preceding the efficacy assessment (see Section 3.9.1.2).

", + "

Patients who successfully complete the study will be eligible for participation in an openlabel extension phase, where every patient will be treated with active agent. The patients who elect to participate in the open-label extension phase will be titrated to their maximally titrated dose. This open-label extension phase will continue until the time the product becomes marketed and is available to the public or until the project is discontinued by the sponsor. Patients may terminate at any time at their request.

", + "

Because patients enrolled in this study will be outpatients, the knowledge that patients have taken the medication as prescribed will be assured in the following ways:

\r\n
    \r\n
  1. Investigators will attempt to select those patients and caregivers who \r\nhave been judged to be compliant.

  2. \r\n
  3. Study medication including unused, partially used, and empty patch \r\ncontainers will be returned at each clinical visit so that the remaining \r\nmedication can be counted by authorized investigator staff (nurse, \r\npharmacist, or physician). The number of patches remaining will be \r\nrecorded on the CRF.

  4. \r\n
  5. Following randomization at Visit 3, patients will be instructed to call \r\nthe site if they have difficulty with application or wearing of patches. If \r\ndaily doses are reduced, improperly administered, or if a patch becomes \r\ndetached and requires application of a new patch on three or more days \r\nin any 30-day period, the CRO research physician will be notified.

  6. \r\n
\r\n

If the daily dose is reduced or improperly administered in the 24 hours prior to any scheduled clinic visit, the visit should be rescheduled (except for early termination and retrieval visits).

", + "

To ensure both the safety of participants in the study, and the collection of accurate, complete, and reliable data, Lilly or its representatives will perform the following activities:

\r\n\r\n

To ensure the safety of participants in the study and to ensure accurate, complete, and reliable data, the investigator will do the following:

\r\n\r\n

Lilly or its representatives may periodically check a sample of the patient data recorded against source documents at the study site. The study may be audited by Lilly Medical Quality Assurance (MQA) and/or regulatory agencies at any time. Investigators will be given notice before an MQA audit occurs.

", + "
", + "

In general, all patients will be included in all analyses of efficacy if they have a baseline measurement and at least one postrandomization measurement. Refer to Section 3.9.1.2. for a discussion of which specific efficacy data will be included in the primary analysis.

\r\n

In the event that the doses of xanomeline TTS are changed after the study starts, the analysis will be of three treatment groups (high dose, low dose, and placebo), even though patients within the high dose treatment group, for example, may not all be at exactly the same dose. Also, if the dose is changed midway through the study, the mean dose within each group will be used in the dose response analysis described in Section 4.3.3.

\r\n

All analyses described below will be conducted using the most current production version of SAS® available at the time of analysis.

", + "

All measures (for example, age, gender, origin) obtained at either Visits 1, 2, or 3, prior to randomization, will be summarized by treatment group and across all treatment groups. The groups will be compared by analysis of variance (ANOVA) for continuous variables and by Pearson's chi-square test for categorical variables. Note that because patients are randomized to 1 of the 3 treatment groups, any statistically significant treatment group differences are by definition a Type I error; however, the resulting p-values will be used as another descriptive statistic to help focus possible additional analyses (for example, analysis of covariance, subset analyses) on those factors that are most imbalanced (that is, that have the smallest p-values).

", + "
", + "

Efficacy measures are described in Section 3.9.1.1. As stated in Section 3.9.1.2, the primary outcome measures are the ADAS-Cog (11) and CIBIC+ instruments. Because both of these variables must reach statistical significance, an adjustment to the nominal p-values is necessary in order to maintain a .05 Type I error rate for this study. This adjustment is described in detail in Section 4.3.5.

\r\n

The DAD will be analyzed with respect to the total score, as well as the subscores of \r\ninitiation, planning and organization, and effective performance. This variable is \r\nconsidered a secondary variable in the US, but is a third primary variable in Europe.

\r\n

The NPI-X is a secondary variable. The primary assessment of this instrument will be for the total score, not including the sleep, appetite, and euphoria domains. This total score is computed by taking the product of the frequency and severity scores and summing them up across the domains. Secondary variables derived from the NPI-X include evaluating each domain/behavior separately. Also, caregiver distress from the NPI-X will be analyzed.

\r\n

ADAS-Cog (14) and each of the 14 individual components will also be analyzed. In addition, a subscore of the ADAS-Cog will be computed and analyzed, based on results from a previous large study of oral xanomeline. This subscore, referred to as ADAS-Cog (4), will be the sum of constructional praxis, orientation, spoken language ability, and word finding difficulty in spontaneous speech.

\r\n

Any computed total score will be treated as missing if more than 30% of the items are missing or scored “not applicable”. For example, when computing ADAS-Cog(11), if 4 or more items are missing, then the total score will not be computed. When one or more items are missing (but not more than 30%), the total score will be adjusted in order to maintain the full range of the scale. For example, ADAS-Cog(11) is a 0-70 scale. If the first item, Word Recall (ranges from 0 to 10), is missing, then the remaining 10 items of the ADAS-Cog(11) will be summed and multiplied by (70 / (70-10) ), or 7/6. This computation will occur for all totals and subtotals of ADAS-Cog and NPI-X. DAD is a 40 item questionnaire where each question is scored as either “0” or “1”. The DAD total score and component scores are reported as percentage of items that are scored “1”. So if items of the DAD are “not applicable” or missing, the percentage will be computed for only those items that are scored. As an example, if two items are missing (leaving 38 that are scored), and there are 12 items scored as “1”, the rest as “0”, then the DAD score is 12/38=.316.

", + "

Baseline data will be collected at Visit 3.

\r\n

The primary analysis of ADAS-Cog (11) and CIBIC+ will be the 24-week endpoint, which is defined for each patient and variable as the last measurement obtained postrandomization (prior to protocol defined reduction in dose).

\r\n

Similar analyses at 24 weeks will be conducted for the secondary efficacy variables. Analysis of patients who complete the 24-week study will also be conducted for all efficacy variables; this is referred to as a “completer” analysis.

\r\n

Additionally, each of the efficacy variables will be analyzed at each time point both as “actual cases,” that is, analyzing the data collected at the various time points, and also as a last-observation-carried-forward (LOCF). Note that the LOCF analysis at 24 weeks is the same as the endpoint analysis described previously.

\r\n

Several additional analyses of NPI-X will be conducted. Data from this instrument will be collected every 2 weeks, and represent not the condition of the patient at that moment in time, but rather the worst condition of the patient in the time period since the most recent NPI-X administration. For this reason, the primary analysis of the NPI-X will be of the average of all postrandomization NPI-X subscores except for the one obtained at Week 2. In the event of early discontinuations, those scores that correspond to the interval between Weeks 2 to 24 will be averaged. The reason for excluding Week 2 data from this analysis is that patients could be confused about when a behavior actually stops after randomization; the data obtained at Week 2 could be somewhat “tainted.” Also, by requiring 2 weeks of therapy prior to use of the NPI-X data, the treatment difference should be maximized by giving the drug 2 weeks to work, thereby increasing the statistical power. Secondary analyses of the NPI-X will include the average of all postrandomization weeks, including measures obtained at Weeks 2 and 26.

", + "

The primary method to be used for the primary efficacy variables described in Sections 4.3.1 and 4.3.2 will be analysis of covariance (ANCOVA), except for CIBIC+ which is a score that reflects change from baseline, so there is no corresponding baseline CIBIC+ score. Effects in the ANCOVA model will be the corresponding baseline score, investigator, and treatment. CIBIC+ will be analyzed by analysis of variance (ANOVA), with effects in the model being investigator and treatment. Investigator-by-treatment interaction will be tested in a full model prior to conducting the primary ANCOVA or ANOVA (see description below).

\r\n

Because 3 treatment groups are involved, the primary analysis will be the test for linear dose response in the ANCOVA and ANOVA models described in the preceding paragraph. The result is then a single p-value for each of ADAS-Cog and CIBIC+.

\r\n

Analysis of the secondary efficacy variables will also be ANCOVA. Pairwise treatment comparisons of the adjusted means for all efficacy variables will be conducted using a LSMEANS statement within the GLM procedure.

\r\n

Investigator-by-treatment interaction will be tested in a full ANCOVA or ANOVA model, which takes the models described above, and adds the interaction term to the model. Interaction will be tested at α = .10 level. When the interaction is significant at this level, the data will be examined for each individual investigator to attempt to identify the source of the significant interaction. When the interaction is not significant, this term will be dropped from the model as described above, to test for investigator and treatment main effects. By doing so, all ANCOVA and ANOVA models will be able to validly test for treatment differences without weighting each investigator equally, which is what occurs when using Type III sums of squares (cell means model) with the interaction term present in the model. This equal weighting of investigators can become a serious problem when sample sizes are dramatically different between investigators.

\r\n

For all ANOVA and ANCOVA models, data collected from investigators who enrolled fewer than 3 patients in any one treatment group will be combined prior to analysis. If this combination still results in a treatment group having fewer than 3 patients in any one treatment group, then this group of patients will be combined with the next fewestenrolling investigator. In the event that there is a tie for fewest-enrolling investigator, one of these will be chosen at random by a random-number generator.

\r\n

The inherent assumption of normally distributed data will be evaluated by generating output for the residuals from the full ANCOVA and ANOVA models, which include the interaction term, and by testing for normality using the Shapiro-Wilk test from PROC UNIVARIATE. In the event that the data are predominantly nonnormally distributed, analyses will also be conducted on the ranked data. This rank transformation will be applied by ranking all the data for a particular variable, across all investigators and treatments, from lowest to highest. Integer ranks will be assigned starting at 1; mean ranks will be assigned when ties occur.

\r\n

In addition, the NPI-X will be analyzed in a manner similar to typical analyses of adverse events. In this analysis, each behavior will be considered individually. This analysis is referred to as “treatment-emergent signs and symptoms” (TESS) analysis. For each behavior, the patients will be dichotomized into 1 of 2 groups: those who experienced the behavior for the first time postrandomization, or those who had the quotient between frequency and severity increase relative to the baseline period defines one group. All other patients are in the second group. Treatments will be compared for overall differences by Cochran-Mantel-Haentzel (CMH) test referred to in SAS® as “row mean scores differ,” 2 degrees of freedom. The CMH correlation statistic (1 degree of freedom test), will test for increasing efficacy with increasing dose (trend test).

", + "

All comparisons between xanomeline and placebo with respect to efficacy variables should be one-sided. The justification for this follows.

\r\n

The statistical hypothesis that is tested needs to be consistent with the ultimate data-based decision that is reached. When conducting placebo-controlled trials, it is imperative that the drug be demonstrated to be superior in efficacy to placebo, since equivalent or worse efficacy than placebo will preclude approvability. Consequently, a one-sided test for efficacy is required.

\r\n

The null hypothesis is that the drug is equal or worse than placebo. The alternative hypothesis is that the drug has greater efficacy than placebo. A Type I error occurs only when it is concluded that a study drug is effective when in fact it is not. This can occur in only one tail of the distribution of the treatment difference. Further details of the arguments for one-sided tests in placebo-controlled trials are available in statistical publications (Fisher 1991; Koch 1991; Overall 1991; and Peace 1991).

\r\n

The argument for one-sided tests does not necessarily transfer to safety measures, in general, because one can accept a certain level of toxicity in the presence of strong efficacy. That is, safety is evaluated as part of a benefit/risk ratio.

\r\n

Note that this justification is similar to that used by regulatory agencies worldwide that routinely require one-sided tests for toxicological oncogenicity studies. In that case, the interest is not in whether a drug seems to lessen the occurrence of cancer; the interest is in only one tail of the distribution, namely whether the drug causes cancer to a greater extent than the control.

\r\n

Different regulatory agencies require different type I error rates. Treatment differences that are significant at the .025 α-level will be declared to be “statistically significant.” When a computed p-value falls between .025 and .05, the differences will be described as “marginally statistically significant.” This approach satisfies regulatory agencies who have accepted a one-sided test at the .05 level, and other regulatory agencies who have requested a two-sided test at the .05 level, or equivalently, a one-sided test at the .025 level. In order to facilitate the review of the final study report, two-sided p-values will be presented in addition to the one-sided p-values.

", + "

When there are multiple outcomes, and the study drug is declared to be effective when at least one of these outcomes achieves statistical significance in comparison with a placebo control, a downward adjustment to the nominal α-level is necessary. A well-known simple method is the Bonferroni method, that divides the overall Type I error rate, usually .05, by the number of multiple outcomes. So, for example, if there are two multiple outcomes, the study drug is declared to be effective if at least one of the two outcomes is significant at the .05/2 or .025 level.

\r\n

However, when one has the situation that is present in this study, where there are 2 (or 3 for Europe) outcome variables, each of which must be statistically significant, then the adjustment of the nominal levels is in the opposite direction, that is upwards, in order to maintain an overall Type 1 error rate of .05.

\r\n

In the case of two outcomes, ADAS-Cog (11) and CIBIC+, if the two variables were completely independent, then each variable should be tested at the nominal α-level of .05 1/2 = .2236 level. So if both variables resulted in a nominal p-value less than or equal to .2236, then we would declare the study drug to be effective at the overall Type 1 error rate of .05.

\r\n

We expect these two outcome measures to be correlated. From the first large-scale \r\nefficacy study of oral xanomeline, Study MC-H2Q-LZZA, the correlation between \r\nCIBIC+ and the change in ADAS-Cog(11) from baseline was .252. Consequently, we

\r\n

plan to conduct a randomization test to combine these two dependent dose-response p-values into a single test, which will then be at the .05 Type I error level. Because there will be roughly 300!/(3 * 100!) possible permutations of the data, random data permutations will be sampled (10,000 random permutations).

\r\n

Designate the dose response p-values as p1 and p2 (computed as one-sided p-values), for ADAS-Cog(11) and CIBIC+, respectively. The rejection region is defined as

\r\n

[ {p1 ≤ α and p2 ≤ α} ].

\r\n

The critical value, α, will be determined from the 10,000 random permutations by choosing the value of α to be such that 2.5% of the 10,000 computed pairs of dose response p-values fall in the rejection region. This will correspond to a one-sided test at the .025 level, or equivalently a two-sided test at the .05 level. In addition, by determining the percentage of permuted samples that are more extreme than the observed data, a single p-value is obtained.

", + "

Although safety data is collected at the 24 week visit for retrieved dropouts, these data will not be included in the primary analysis of safety.

\r\n

Pearson's chi-square test will be used to analyze 3 reasons for study discontinuation (protocol completed, lack of efficacy, and adverse event), the incidence of abnormal (high or low) laboratory measures during the postrandomization phase, and the incidence of treatment-emergent adverse events. The analysis of laboratory data is conducted by comparing the measures to the normal reference ranges (based on a large Lilly database), and counting patients in the numerator if they ever had a high (low) value during the postrandomization phase.

\r\n

Additionally, for the continuous laboratory tests, an analysis of change from baseline to endpoint will be conducted using the same ANOVA model described for the efficacy measures in Section 4.3. Because several laboratory analytes are known to be nonnormally distributed (skewed right), these ANOVAs will be conducted on the ranks.

\r\n

Several outcome measures will be extracted and analyzed from the Ambulatory ECG tapes, including number of pauses, QT interval, and AV block (first, second, or third degree). The primary consideration will be the frequency of pauses. The number of pauses greater than or equal to 2, 3, 4, 5 and 6 seconds will be tabulated. Primary analysis will focus on the number of pauses greater than or equal to 3 seconds. Due to possible outliers, these data will be analyzed as the laboratory data, by ANOVA on the ranks.

\r\n

Treatment-emergent adverse events (also referred to as treatment-emergent signs and symptoms, or TESS) are defined as any event reported during the postrandomization period (Weeks 0 - 26) that is worse in severity than during the baseline period, or one that occurs for the first time during the postrandomization period.

", + "

The effect of age, gender, origin, baseline disease severity as measured by MMSE, Apo E, and patient education level upon efficacy will be evaluated if sample sizes are sufficient to warrant such analyses. For example, if all patients are Caucasian, then there is no need to evaluate the co-factor origin. The ANCOVA and ANOVA models described above will be supplemented with terms for the main effect and interaction with treatment. Each co-factor will be analyzed in separate models. The test for treatment-bysubgroup interaction will address whether the response to xanomeline, compared with placebo, is different or consistent between levels of the co-factor.

", + "

Two interim efficacy analyses are planned. The first interim analysis will occur when approximately 50% of the patients have completed 8 weeks; the second interim analysis is to be conducted when approximately 50% of the patients have completed 24 weeks of the study. The purpose of these interim analyses is to provide a rationale for the initiation of subsequent studies of xanomeline TTS, or if the outcome is negative to stop development of xanomeline TTS. The method developed by Enas and Offen (1993) will be used as a guideline as to whether or not to stop one treatment arm, or the study, to declare ineffectiveness. The outcome of the interim analyses will not affect in any way the conduct, results, or analysis of the current study, unless the results are so negative that they lead to a decision to terminate further development of xanomeline TTS in AD. Hence, adjustments to final computed p-values are not appropriate.

\r\n

Planned interim analyses, and any unplanned interim analyses, will be conducted under the auspices of the data monitoring board assigned to this study. Only the data monitoring board is authorized to review completely unblinded interim efficacy and safety analyses and, if necessary, to disseminate those results. The data monitoring board will disseminate interim results only if absolutely necessary. Any such dissemination will be documented and described in the final study report. Study sites will not receive information about interim results unless they need to know for the safety of their patients.

", + "

An analysis of the cardiovascular safety monitoring (see section 3.9.4) will be performed when approximately 25 patients from each treatment arm have completed at least 2 weeks at the treatment arms' respective full dosage (Visit 5). If necessary, this analysis will be repeated every 25 patients per arm. This analysis will be conducted under the auspices of the DSMB. This board membership will be composed of 3 external cardiologists who will be the voting members of the board, a Lilly cardiologist, a Lilly statistician, and the Lilly research physician in charge of the study. Only the DSMB is authorized to review completely unblinded cardiovascular safety analyses and, if necessary, to disseminate those results. The outcome of the cardiovascular safety analyses will determine the need for further Ambulatory ECGs.

", + "

Plasma concentrations of xanomeline will be determined from samples obtained at selected visits (Section 3.9.2). The plasma concentration data for xanomeline, dosing information, and patient characteristics such as weight, gender and origin will be pooled and analyzed using a population pharmacokinetic analysis approach (for example, NONMEM). This approach preserves the individual pharmacokinetic differences through structural and statistical models. The population pharmacokinetic parameters through the structural model, and the interindividual and random residual variability through the components of the statistical models will be estimated. An attempt will also be made to correlate plasma concentrations with efficacy and safety data by means of population pharmacokinetic/pharmacodynamic modeling.

", + "
", + "

In the United States and Canada, the investigator is responsible for preparing the informed consent document. The investigator will use information provided in the current [Clinical Investigator's Brochure or product information] to prepare the informed consent document.

\r\n

The informed consent document will be used to explain in simple terms, before the patient is entered into the study, the risks and benefits to the patient. The informed consent document must contain a statement that the consent is freely given, that the patient is aware of the risks and benefits of entering the study, and that the patient is free to withdraw from the study at any time.

\r\n

As used in this protocol, the term “informed consent” includes all consent and/or assent given by subjects, patients, or their legal representatives.

\r\n

In addition to the elements required by all applicable laws, the 3 numbered paragraphs below must be included in the informed consent document. The language may be altered to match the style of the informed consent document, providing the meaning is unchanged. In some circumstances, local law may require that the text be altered in a way that changes the meaning. These changes can be made only with specific Lilly approval. In these cases, the ethical review board may request from the investigator documentation evidencing Lilly's approval of the language in the informed consent document, which would be different from the language contained in the protocol. Lilly shall, upon request, provide the investigator with such documentation.

\r\n
    \r\n
  1. “I understand that the doctors in charge of this study, or Lilly, may \r\nstop the study or stop my participation in the study at any time, for any \r\nreason, without my consent.”

  2. \r\n
  3. “I hereby give permission for the doctors in charge of this study to \r\nrelease the information regarding, or obtained as a result of, my \r\nparticipation in this study to Lilly, including its agents and contractors; \r\nthe US Food and Drug Administration (FDA) and other governmental \r\nagencies; and to allow them to inspect all my medical records. I \r\nunderstand that medical records that reveal my identity will remain \r\nconfidential, except that they will be provided as noted above or as \r\nmay be required by law.”

  4. \r\n
  5. “If I follow the directions of the doctors in charge of this study and I \r\nam physically injured because of any substance or procedure properly \r\ngiven me under the plan for this study, Lilly will pay the medical \r\nexpenses for the treatment of that injury which are not covered by my \r\nown insurance, by a government program, or by any other third party. \r\nNo other compensation is available from Lilly if any injury occurs.”

  6. \r\n
\r\n

The investigator is responsible for obtaining informed consent from each patient or legal representative and for obtaining the appropriate signatures on the informed consent document prior to the performance of any protocol procedures and prior to the administration of study drug.

", + "

The name and address of the ethical review board are listed on the Investigator/Contacts cover pages provided with this protocol.

\r\n

The investigator will provide Lilly with documentation of ethical review board approval of the protocol and the informed consent document before the study may begin at the site or sites concerned. The ethical review board(s) will review the protocol as required.

\r\n

The investigator must provide the following documentation:

\r\n
", + "

This study will be conducted in accordance with the ethical principles stated in the most recent version of the Declaration of Helsinki or the applicable guidelines on good clinical practice, whichever represents the greater protection of the individual.

\r\n

After reading the protocol, each investigator will sign 2 protocol signature pages and return 1 of the signed pages to a Lilly representative (see Attachment LZZT.10).

", + "
\r\n
\r\n
\r\n

Bierer LM, Haroutunian V, Gabriel S, Knott PJ, Carlin LS, Purohit DP, et al. 1995.
Neurochemical correlates of dementia severity in AD: Relative importance of the cholinergic deficits. J of Neurochemistry 64:749-760.

\r\n
\r\n
\r\n
\r\n
\r\n

Cummings JL, Mega M, Gray K, Rosenberg-Thompson S, et al. 1994. The Neuropsychiatric Inventory: Comprehensive assessment of psychopathology in dementia. Neurology 44:2308-2314.

\r\n
\r\n
\r\n
\r\n
\r\n

Enas GG, Offen WW. 1993. A simple stopping rule for declaring treatment ineffectiveness in clinical trials. J Biop Stat 3(1):13-32.

\r\n
\r\n
\r\n
\r\n
\r\n

Fisher A, Barak D. 1994. Promising therapeutic strategies in Alzheimer's disease based \r\non functionally selective M 1 muscarinic agonists. Progress and perspectives in new \r\nmuscarinic agonists. DN&P 7(8):453-464.

\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n

GLUCAGON for Injection ITO [Package Insert]. Osaka, Japan: Kaigen Pharma Co., Ltd; 2016.Available at:\r\n http://www.pmda.go.jp/PmdaSearch/iyakuDetail/ResultDataSetPDF/130616_7229400D1088_\r\n 1_11.

\r\n
\r\n
\r\n
\r\n
\r\n

Polonsky WH, Fisher L, Hessler D, Johnson N. Emotional distress in the partners of type 1diabetes adults:\r\n worries about hypoglycemia and other key concerns. Diabetes Technol Ther. 2016;18:292-297.

\r\n
\r\n
\r\n
\r\n
\r\n

Fisher LD. 1991. The use of one-sided tests in drug trials: an FDA advisory committee \r\nmember's perspective. J Biop Stat 1:151-6.

\r\n
\r\n
\r\n
\r\n
\r\n

Koch GG. 1991. One-sided and two-sided tests and p-values. J Biop Stat 1:161-70.

\r\n
\r\n
\r\n
\r\n
\r\n

Overall JE. 1991. A comment concerning one-sided tests of significance in new drug \r\napplications. J Biop Stat 1:157-60.

\r\n
\r\n
\r\n
\r\n
\r\n

Peace KE. 1991. Oneside or two-sided p-values: which most appropriately address the \r\nquestion of drug efficacy? J Biop Stat 1:133-8.

\r\n
\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The following SoA timelines are auto generated using the detailed study design held within the USDM.

\r\n
\r\n

Timeline: Main Timeline, Potential subject identified

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X1

X

X

X

X

X

X

X

X

X

X

X

X2

X

X

X

X

X3

X

X

X

X

X4

X

X

X

X

X5

X

X

X

X

X

X

X

X

X

X

X

X

X

X

1

Performed if patient is an insulin-dependent diabetic

2

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

3

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

4

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

5

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

Timeline: Adverse Event Timeline, Subject suffers an adverse event

X

Timeline: Early Termination Timeline, Subject terminates the study early

X

", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "

Sponsor Confidentiality Statement:

Full Title:

Trial Acronym:

Protocol Identifier:

Original Protocol:

Version Number:

Version Date:

Amendment Identifier:

Amendment Scope:

Compound Codes(s):

Compound Name(s):

Trial Phase:

Short Title:

Sponsor Name and Address:

,

Regulatory Agency Identifier Number(s):

Spondor Approval Date:

", + "
Committees\r\n

A Data Safety Monitoring Board (DSMB), chaired by an external cardiologist, will meet after 75, 150, 225, and 300 patients have completed 1 month of treatment. The DSMB will review cardiovascular findings to decide if discontinuation of the study or any treatment arm is appropriate, if additional cardiovascular monitoring is required, if further cardiovascular monitoring is unnecessary, or if adjustment of dose within a treatment arm (or arms) is appropriate (see Section 3.9.4).

", + "
\"Alt\r\n

Figure LZZT.1. Illustration of study design for Protocol H2Q-MC-LZZT(c).

\r\n

Following informed consent, patients will be screened at Visit 1. At screening, patients will undergo complete neuropsychiatric assessment, psychometric testing, and general medical assessment (including medical history, pre-existing conditions, physical examination). In addition, vital signs, temperature, medication history, electrocardiogram (ECG), chest x-ray, and safety laboratories will be obtained. During the screening visit, patients will wear a placebo TTS to determine willingness and ability to comply with transdermal administration procedures. If patients have not had central nervous system (CNS) imaging in the previous 12 months, a computed tomography (CT) or magnetic resonance imaging (MRI) scan will be obtained. If patients are insulin dependent diabetics, a hemoglobin A 1c will be obtained. Screening exams and procedures may be performed after Visit 1; however, their results must be completed and available prior to randomization. The screening process should occur within 2 weeks of randomization (Visit 3 of the study).

\r\n

Patients who meet enrollment criteria from Visit 1 will proceed to Visit 2 at which time they will undergo a 24-hour Ambulatory ECG. At Visit 3 the Ambulatory ECG will be removed and patients will be randomized to 1 of 3 treatment arms. The treatment arms will include a placebo arm, a low-dose xanomeline arm (50 cm 2 TTS Formulation E, 54 mg xanomeline), and a high-dose xanomeline arm (75 cm 2 TTS Formulation E, 81 mg xanomeline). All patients receiving xanomeline will be started at 50 cm 2 TTS Formulation E. For the first 8 weeks of treatment, patients will be assessed at clinic visits every 2 weeks and, thereafter, at clinic visits every 4 weeks. Patients who discontinue prior to Visit 12 (Week 24) will be brought back for full efficacy assessments at or near to 24 weeks, whenever possible.

\r\n

At Visits 3, 8, 10, and 12, efficacy instruments (ADAS-Cog, CIBIC+, and DAD) will be administered. NPI-X will be administered at 2-week intervals either at clinic visits or via a telephone interview. Vital signs, temperature, and an assessment of adverse events will be obtained at all clinic visits. An electrocardiogram (ECG), and chemistry/hematology safety labs will be obtained at Visits 4, 5, 7, 8, 9, 10, 11, 12, and 13. Urinalysis will be done at Visits 4, 9, and 12. Use of concomitant medications will be collected at Visits 3, 4, 5, 7, 8, 9, 10, 11, 12, and 13. Plasma levels of xanomeline and metabolites will be obtained at Visits 3, 4, 5, 7, 9, and 11. At Visits 3, 4, 5, 7, 8, 9, 10, 11, and 12, medications will be dispensed to the patients.

\r\n

Visits 1 through 13 should be scheduled relative to Visit 3 (Week 0 - randomization). Visits 4, 5, 7, 8, and 13 should occur within 3 days of their scheduled date. Visits 9, 10, 11, and 12 should occur within 4 days of their scheduled date. At Visit 13 patients will be given the option to enter the open-label extension phase (see Section 3.10.3. Study Extensions).

", + "
\r\n
\r\n

Note:

\r\n

The following SoA timelines are auto generated using the detailed study design held within the USDM.

\r\n
\r\n

Timeline: Main Timeline, Potential subject identified

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X1

X

X

X

X

X

X

X

X

X

X

X

X2

X

X

X

X

X3

X

X

X

X

X4

X

X

X

X

X5

X

X

X

X

X

X

X

X

X

X

X

X

X

X

1

Performed if patient is an insulin-dependent diabetic

2

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

3

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

4

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

5

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

Timeline: Adverse Event Timeline, Subject suffers an adverse event

X

Timeline: Early Termination Timeline, Subject terminates the study early

X

", + "

The primary objectives of this study are

\r\n
", + "

The secondary objectives of this study are

\r\n
", + "

Approximately 300 patients will be enrolled (see Schedule of Events for Protocol H2Q-MC-LZZT(c), Attachment LZZT.1).

\r\n

Duration

\r\n

SOMETHING HERE

\r\n

Patients with probable mild to moderate AD will be studied in a randomized, double-blind, parallel (3 arm), placebo-controlled trial of 26 weeks duration. The study will be conducted on an outpatient basis.

\r\n

At Visit 1, patients who meet the enrollment criteria of Mini-Mental State Examination (MMSE) score of 10 to 23 (Attachment LZZT.6), Hachinski Ischemia Score ≤4 (Attachment LZZT.8), a physical exam, safety labs, ECG, and urinalysis, will proceed to Visit 2 and Visit 3. At Visit 3, patients whose CNS imaging and other pending labs from Visit 1 satisfy the inclusion criteria (Section 3.4.2.1) will be enrolled in the study. Approximately 300 patients with a diagnosis of probable mild to moderate AD will be enrolled in the study.

", + "

Patients may be included in the study only if they meet all the following criteria:

\r\n
01
02
03
04
05
06
07
08
", + "

Patients will be excluded from the study for any of the following reasons:

\r\n
09
10
11
12
13
14
15
16b
17
18
19
20
21
22
23
24
25
26
27b
28b
29b
30b
31b
", + "
\r\n
\r\n
\r\n

The information contained in this clinical study protocol is

Copyright © 2006 Eli Lilly and Company.

\r\n
\r\n
\r\n
\r\n
\r\n

\r\n
\r\n
\r\n
\r\n
\r\n

\r\n
\r\n
\r\n
\r\n
\r\n

\r\n
\r\n
\r\n
", + "

The M1 muscarinic-cholinergic receptor is 1 of 5 characterized muscarinic-cholinergic receptor subtypes (Fisher and Barak 1994). M1 receptors in the cerebral cortex and hippocampus are, for the most part, preserved in Alzheimer's disease (AD), while the presynaptic neurons projecting to these receptors from the nucleus basalis of Meynert degenerate (Bierer et al. 1995). The presynaptic loss of cholinergic neurons has been correlated to the antimortum cognitive impairment in AD patients, prompting speculation that replacement therapy with cholinomimetics will alleviate the cognitive dysfunction of the disorder (Fisher and Barak 1994).

\r\n

Xanomeline is a novel M1 agonist which has shown high affinity for the M1 receptor subtype (in transfected cells), and substantially less or no affinity for other muscarinic subtypes. Positron emission tomography (PET) studies of 11C-labeled xanomeline in cynomolgus monkeys have suggested that the compound crosses the blood-brain barrier and preferentially binds the striatum and neocortex.

\r\n

Clinical development of an oral formulation of xanomeline for the indication of mild and moderate AD was initiated approximately 4 years ago. A large-scale study of safety and efficacy provided evidence that an oral dosing regimen of 75 mg three times daily (TID) may be associated with enhanced cognition and improved clinical global impression, relative to placebo. As well, a dramatic reduction in psychosis, agitation, and other problematic behaviors, which often complicate the course of the disease, was documented. However, the discontinuation rate associated with this oral dosing regimen was 58.6%, and alternative clinical strategies have been sought to improve tolerance for the compound.

\r\n

To that end, development of a Transdermal Therapeutic System (TTS) has been initiated. Relative to the oral formulation, the transdermal formulation eliminates high concentrations of xanomeline in the gastrointestinal (GI) tract and presystemic (firstpass) metabolism. Three transdermal delivery systems, hereafter referred to as the xanomeline TTS Formulation A, xanomeline TTS Formulation B, and xanomeline TTS formulation E have been manufactured by Lohman Therapy Systems GmbH of Andernach Germany. TTS Formulation A is 27 mg xanomeline freebase in a 25-cm2 matrix. TTS Formulation B is 57.6 mg xanomeline freebase in a 40-cm2 matrix. Formulation E has been produced in 2 patch sizes: 1) 54 mg xanomeline freebase with 0.06 mg Vitamin E USP in a 50-cm2 matrix and 2) 27 mg xanomeline freebase with 0.03 mg Vitamin E USP in a 25-cm2 matrix. For a detailed description of the composition of these formulations please refer to Part II, Section 14 of the Xanomeline (LY246708) Clinical Investigator's Brochure. For characterization of the safety, tolerance, and pharmacokinetics of xanomeline TTS Formulations A, B, and E, please refer to Part II, Sections 7, 8, and 10 of the Xanomeline (LY246708) Clinical Investigator's Brochure. Formulation E will be studied in this protocol, H2Q-MC-LZZT(c).

", + "
", + "

The primary objectives of this study are

\r\n
", + "

The secondary objectives of this study are

\r\n
", + "
", + "

Patients with probable mild to moderate AD will be studied in a randomized, double-blind, parallel (3 arm), placebo-controlled trial of 26 weeks duration. The study will be conducted on an outpatient basis. Approximately 300 patients will be enrolled (see Schedule of Events for Protocol H2Q-MC-LZZT(c), Attachment LZZT.1).

\r\n

Following informed consent, patients will be screened at Visit 1. At screening, patients will undergo complete neuropsychiatric assessment, psychometric testing, and general medical assessment (including medical history, pre-existing conditions, physical examination). In addition, vital signs, temperature, medication history, electrocardiogram (ECG), chest x-ray, and safety laboratories will be obtained. During the screening visit, patients will wear a placebo TTS to determine willingness and ability to comply with transdermal administration procedures. If patients have not had central nervous system (CNS) imaging in the previous 12 months, a computed tomography (CT) or magnetic resonance imaging (MRI) scan will be obtained. If patients are insulin dependent diabetics, a hemoglobin A 1c will be obtained. Screening exams and procedures may be performed after Visit 1; however, their results must be completed and available prior to randomization. The screening process should occur within 2 weeks of randomization (Visit 3 of the study).

\r\n

Patients who meet enrollment criteria from Visit 1 will proceed to Visit 2 at which time they will undergo a 24-hour Ambulatory ECG. At Visit 3 the Ambulatory ECG will be removed and patients will be randomized to 1 of 3 treatment arms. The treatment arms will include a placebo arm, a low-dose xanomeline arm (50 cm 2 TTS Formulation E, 54 mg xanomeline), and a high-dose xanomeline arm (75 cm 2 TTS Formulation E, 81 mg xanomeline). All patients receiving xanomeline will be started at 50 cm 2 TTS Formulation E. For the first 8 weeks of treatment, patients will be assessed at clinic visits every 2 weeks and, thereafter, at clinic visits every 4 weeks. Patients who discontinue prior to Visit 12 (Week 24) will be brought back for full efficacy assessments at or near to 24 weeks, whenever possible.

\r\n

A Data Safety Monitoring Board (DSMB), chaired by an external cardiologist, will meet after 75, 150, 225, and 300 patients have completed 1 month of treatment. The DSMB will review cardiovascular findings to decide if discontinuation of the study or any treatment arm is appropriate, if additional cardiovascular monitoring is required, if further cardiovascular monitoring is unnecessary, or if adjustment of dose within a treatment arm (or arms) is appropriate (see Section 3.9.4).

\r\n

At Visits 3, 8, 10, and 12, efficacy instruments (ADAS-Cog, CIBIC+, and DAD) will be administered. NPI-X will be administered at 2-week intervals either at clinic visits or via a telephone interview. Vital signs, temperature, and an assessment of adverse events will

\r\n

be obtained at all clinic visits. An electrocardiogram (ECG), and chemistry/hematology safety labs will be obtained at Visits 4, 5, 7, 8, 9, 10, 11, 12, and 13. Urinalysis will be done at Visits 4, 9, and 12. Use of concomitant medications will be collected at Visits 3, 4, 5, 7, 8, 9, 10, 11, 12, and 13. Plasma levels of xanomeline and metabolites will be obtained at Visits 3, 4, 5, 7, 9, and 11. At Visits 3, 4, 5, 7, 8, 9, 10, 11, and 12, medications will be dispensed to the patients.

\r\n

Visits 1 through 13 should be scheduled relative to Visit 3 (Week 0 - randomization). Visits 4, 5, 7, 8, and 13 should occur within 3 days of their scheduled date. Visits 9, 10, 11, and 12 should occur within 4 days of their scheduled date. At Visit 13 patients will be given the option to enter the open-label extension phase (see Section 3.10.3. Study Extensions).

\r\n\"Alt\r\n

Figure LZZT.1. Illustration of study design for Protocol H2Q-MC-LZZT(c).

", + "

Previous studies of the oral formulation have shown that xanomeline tartrate may improve behavior and cognition. Effects on behavior are manifest within 2 to 4 weeks of initiation of treatment. The same studies have shown that 8 to 12 weeks are required to demonstrate effects on cognition and clinical global assessment. This study is intended to determine the acute and chronic effects of the TTS formulation in AD; for that reason, the study is of 26 weeks duration. Dosage specification has been made on the basis of tolerance to the xanomeline TTS in a clinical pharmacology study (H2Q-EW-LKAA), and target plasma levels as determined in studies of the oral formulation of xanomeline (H2Q-MC-LZZA).

\r\n

The parallel dosing regimen maximizes the ability to make direct comparisons between the treatment groups. The use of placebo allows for a blinded, thus minimally biased, study. The placebo treatment group is a comparator group for efficacy and safety assessment.

\r\n

Two interim analyses are planned for this study. The first interim analysis will occur when 50% of the patients have completed Visit 8 (8 weeks). If required, the second interim analysis will occur when 50% of the patients have completed Visit 12 (24 weeks). (See Section 4.6, Interim Analyses.)

", + "

The name, title, and institution of the investigator(s) is/are listed on the Investigator/Contacts cover pages provided with this protocol. If the investigator is changed after the study has been approved by an ethical review board, or a regulatory agency, or by Lilly, this addition will not be considered a change to the protocol. However, the Investigator/Contacts cover pages will be updated to provide this information.

", + "

The final report coordinating investigator will sign the final clinical study report for this study, indicating agreement with the analyses, results, and conclusions of the report.

\r\n

The investigator who will serve as the final report coordinating investigator will be an individual that is involved with the design and analysis of the study. This final report coordinating investigator will be named by the sponsor of the study.

", + "
", + "

An Ethical Review Board (ERB) approved informed consent will be signed by the patient (and/or legal representative) and caregiver after the nature of the study is explained.

", + "

For Lilly studies, the following definitions are used:

\r\n
\r\n
Screen
\r\n
\r\n

Screening is the act of determining if an individual meets minimum requirements to become part of a pool of potential candidates for participation in a clinical study.

\r\n

In this study, screening will include asking the candidate preliminary questions (such as age and general health status) and conducting invasive or diagnostic procedures and/or tests (for example, diagnostic psychological tests, x-rays, blood draws). Patients will sign the consent at their screening visit, thereby consenting to undergo the screening procedures and to participate in the study if they qualify.

\r\n
\r\n
\r\n
\r\n
To enter
\r\n
\r\n

Patients entered into the study are those from whom informed consent for the study has been obtained. Adverse events will be reported for each patient who has entered the study, even if the patient is never assigned to a treatment group (enrolled).

\r\n
\r\n
\r\n
\r\n
To enroll
\r\n
\r\n

Patients who are enrolled in the study are those who have been assigned to a treatment group. Patients who are entered into the study but fail to meet criteria specified in the protocol for treatment assignment will not be enrolled in the study.

\r\n
\r\n
\r\n

At Visit 1, patients who meet the enrollment criteria of Mini-Mental State Examination (MMSE) score of 10 to 23 (Attachment LZZT.6), Hachinski Ischemia Score ≤4 (Attachment LZZT.8), a physical exam, safety labs, ECG, and urinalysis, will proceed to Visit 2 and Visit 3. At Visit 3, patients whose CNS imaging and other pending labs from Visit 1 satisfy the inclusion criteria (Section 3.4.2.1) will be enrolled in the study. Approximately 300 patients with a diagnosis of probable mild to moderate AD will be enrolled in the study.

", + "

Patients may be included in the study only if they meet all the following criteria:

\r\n
01
02
03
04
05
06
07
08
", + "

Patients will be excluded from the study for any of the following reasons:

\r\n
09
10
11
12
13
14
15
16b
17
18
19
20
21
22
23
24
25
26
27b
28b
29b
30b
31b
", + "

The criteria for enrollment must be followed explicitly. If there is inadvertent enrollment of individuals who do not meet enrollment criteria, these individuals should be discontinued from the study. Such individuals can remain in the study only if there are ethical reasons to have them continue. In these cases, the investigator must obtain approval from the Lilly research physician for the study participant to continue in the study (even if the study is being conducted through a contract research organization).

", + "

Probable AD will be defined clinically by NINCDS/ADRDA guidelines as follows:

\r\n
    \r\n
  • Diagnosis of probable AD as defined by National Institute of Neurological and Communicative Disorders and Stroke (NINCDS) and the Alzheimer's Disease and Related Disorders Association (ADRDA) guidelines.

  • \r\n
  • Mild to moderate severity of AD will be defined by the Mini-Mental State Exam as follows:

  • \r\n
  • Mini-Mental State Examination (MMSE) score of 10 to 23.

  • \r\n
  • The absence of other causes of dementia will be performed by clinical opinion and by the following:

  • \r\n
  • Hachinski Ischemic Scale score of ≤4.

  • \r\n
  • CNS imaging (CT scan or MRI of brain) compatible with AD within past 1 year (see Section 3.4.2.1).

  • \r\n
", + "

Approximately 100 patients will be randomized to each of the 3 treatment groups. Previous experience with the oral formulation of xanomeline suggests that this sample size has 90% power to detect a 3.0 mean treatment difference in ADAS-Cog (p<.05, two-sided), based on a standard deviation of 6.5. Furthermore, this sample size has 80% power to detect a 0.36 mean treatment difference in CIBIC+ (p<.05, two-sided), based on a standard deviation of 0.9.

", + "

Commencing at Visit 1, all patients will be assigned an identification number. This identification number and the patient's three initials must appear on all patient-related documents submitted to Lilly.

\r\n

When qualified for enrollment at Visit 3 the patient will be randomized to 1 of 3 treatment arms.

", + "
", + "
\r\n\r\n\r\n\r\n\r\n\r\n\r\n

Primary Study Material:

Xanomeline

TTS (adhesive patches)

50 cm 2 , 54 mg* 25 cm 2 , 27 mg*

Comparator Material:

Placebo

TTS

Identical in appearance to primary study material

\r\n

*All doses are measured in terms of the xanomeline base.

\r\n

Patches should be stored at controlled room temperature, and all used patches must be handled and disposed of as biohazardous waste.

\r\n

For a detailed description of the composition of these formulations please refer to Part II, Section 14 of the Xanomeline (LY246708) Clinical Investigator's Brochure.

", + "

To test acute tolerance of transdermal formulation, patients will have a TTS (placebo) administered at the start of Visit 1, and removed at the conclusion of Visit 1. The patient's and caregiver's willingness to comply with 26 weeks of transdermal therapy should be elicited, and those patients/caregivers unwilling to comply should be excluded.

\r\n

Upon enrollment at Visit 3, and on the morning of each subsequent day of therapy , xanomeline or placebo will be administered with the application of 2 adhesive patches, one 50 cm2 in area, the other 25 cm2 in area. Each morning, prior to the application of the patches, hydrocortisone cream (1%) should be applied to the skin at the intended site of administration, rubbed in, and allowed to penetrate for approximately 30 minutes. Thereafter, excess cream should be wiped away and the patches applied.

\r\n

The patches are to be worn continuously throughout the day, for a period of approximately 12 to 14 hours, and removed in the evening. After removal of the patches, hydrocortisone cream (1%) should be applied locally to the site of administration.

\r\n

Patches should be applied to a dry, intact, non-hairy area. Applying the patch to a shaved area is not recommended. The application site of the patches should be rotated according to the following schedule:

\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n

Day

Patch Location

Sunday

right or left upper arm

Monday

right or left upper back

Tuesday

right or left lower back (above belt line)

Wednesday

right or left buttocks

Thursday

right or left mid-axillary region

Friday

right or left upper thigh

Saturday

right or left upper chest

\r\n

Patients and caregivers are free to select either the left or right site within the constraints of the rotation schedule noted above. Patches should be applied at approximately the same time each day. For patients who habitually bathe in the morning, the patient should bathe prior to application of new patches. Every effort should be taken to allow for morning administration of the patches. Exceptions allowing administration of TTS patches at night instead of in the morning will be made on a case-by-case basis by the CRO medical monitor. In the event that some adhesive remains on the patient's skin and cannot be removed with normal bathing, a special solution will be provided to remove the adhesive.

\r\n

Following randomization at Visit 3, patients will be instructed to call the site if they have difficulty with application or wearing of patches. In the event that a patch becomes detached, a new patch of the same size should be applied (at earliest convenience) to an area of the dermis adjacent to the detachment site, and the rotation schedule should be resumed the following morning. If needed, the edges of the patch may be secured with a special adhesive tape that will be provided. If daily doses are reduced, improperly administered, or if a patch becomes detached and requires application of a new patch on three or more days in any 30-day period, the CRO research physician will be notified.

\r\n

If the daily dose is reduced or improperly administered in the 24 hours prior to any scheduled clinic visit, the visit should be rescheduled (except for early termination and retrieval visits).

\r\n

Patients must be instructed to return all used and unused study drug to the investigator at each visit for proper disposal and CT reconciliation by the investigator.

", + "

The study will be double-blind. To further preserve the blinding of the study, only a minimum number of Lilly and CRO personnel will see the randomization table and codes before the study is complete.

\r\n

Emergency codes generated by a computer drug-labeling system will be available to the investigator. These codes, which reveal the patients treatment group, may be opened during the study only if the choice of follow-up treatment depends on the patient's therapy assignment.

\r\n

The investigator should make every effort to contact the clinical research physician prior to unblinding a patient's therapy assignment. If a patient's therapy assignment is unblinded, Lilly must be notified immediately by telephone. After the study, the investigator must return all sealed and any opened codes.

", + "

Intermittent use of chloral hydrate, zolpidem, or lorazepam is permitted during this clinical trial as indicated for agitation or sleep. If medication is required for agitation for a period exceeding 1 week, a review of the patient's status should be made in consultation with the CRO research physician. Caregivers and patients should be reminded that these medications should not be taken within 24 hours of a clinic visit (including the enrollment visit), and administration of efficacy measures should be deferred if the patient has been treated with these medications within the previous 24 hours.

\r\n

If an antihistamine is required during the study, Claritin® (loratadine) or Allegra® (fexofenadine hydrochloride) are the preferred agents, but should not be taken within 24 hours of a clinic visit. Intermittent use (per package insert) of antitussives (containing antihistamines or codeine) and select narcotic analgesics (acetaminophen with oxycodone, acetaminophen with codeine) are permitted during the trial. Caregivers and patients should be reminded that antihistamines and narcotics should not be taken within 3 days of a clinic efficacy visit (including enrollment visit). If an H 2 blocker is required during the study, Axid® (nizatidine) will be permitted on a case-by-case basis by the CRO medical monitor. For prostatic hypertrophy, small doses (2 mg per day) of Hytrin® (terazosin) or Cardura® (doxazosin) will be permitted on a case-by-case basis. Please consult the medical monitor. The calcium channel blockers Cardene® (nicardipine),

\r\n

Norvasc® (amlodipine), and DynaCirc® (isradipine) are allowed during the study. If a patient has been treated with any medication within disallowed time periods prior to the clinic visit, efficacy measures should be deferred.

\r\n

Other classes of medications not stated in Exclusion Criteria, Section 3.4.2.2, will be permitted. Patients who require treatment with an excluded medication (Section 3.4.2.2) will be discontinued from the study following consultation with the CRO research physician.

", + "
", + "

See Schedule of Events, Attachment LZZT.1 for the times of the study at which efficacy data will be collected.

", + "

The following measures will be performed in the course of the study. At Visits 3, 8, 10, and 12, ADAS-Cog, CIBIC+, and DAD will be administered. NPI-X will be administered at 2-week intervals either at clinic visits or via a telephone interview. Efficacy measures will also be collected at early termination visits, and at the retrieval visit. The neuropsychological assessment should be performed first; other protocol requirements, such as labs and the physical, should follow.

\r\n
    \r\n
  1. Alzheimer's Disease Assessment Scale - Cognitive Subscale (ADAS-Cog): ADAS-Cog is an established measure of cognitive function in Alzheimer's Disease. This scale has been incorporated into this study by permission of Dr. Richard C. Mohs and the American Journal of Psychiatry and was adapted from an article entitled, “The Alzheimer's Disease Assessment Scale (ADAS),” which was published in the American Journal of Psychiatry, Volume No.141, pages 1356-1364, November, 1984, Copyright 1984.

    \r\n

    The ADAS-Cog (11) and the ADAS-Cog (14): The ADAS-Cog (11) is a standard 11-item instrument used to assess word recall, naming objects, commands, constructional praxis, ideational praxis, orientation, word recognition tasks, spoken language ability, comprehension, word finding difficulty, and recall of test instructions. For the purposes of this study, three items (delayed word recall, attention/visual search task, and maze solution) have been added to the ADAS-Cog (11) to assess the patient's attention and concentration. The 14 item instrument will be referred to as the ADAS-Cog (14). At each efficacy visit, all 14 items will be assessed, and in subsequent data analyses, performance on the ADAS-Cog (14) and performance on the subset ADAS-Cog (11) will be considered.

  2. \r\n
  3. Video-referenced Clinician's Interview-Based Impression of Change (CIBIC+): The CIBIC+ is an assessment of the global clinical status relative to baseline. The CIBIC+ used in this study is derived from the Clinical Global Impression of Change, an instrument in the public domain, developed by the National Institute on Aging Alzheimer's Disease Study Units Program (1 U01 AG10483; Leon Thal, Principal Investigator). The instrument employs semi-structured interviews with the patient and caregiver, to assess mental/cognitive state, behavior, and function. These domains are not individually scored, but rather are aggregated in the assignment of a global numeric score on a 1 to 7 scale (1 = marked improvement; 4 = no change; and 7 = marked worsening).

    \r\n

    The clinician assessing CIBIC+ will have at least one year of experience with the instrument and will remain blinded to all other efficacy and safety measures.

  4. \r\n
  5. Revised Neuropsychiatric Inventory (NPI-X): The NPI-X is an assessment of change in psychopathology in patients with dementia. The NPI-X is administered to the designated caregiver. This instrument has been revised from its original version (Cummings et al. 1994) and incorporated into this study with the permission of Dr. Jeffrey L. Cummings.

  6. \r\n
  7. Disability Assessment for Dementia (DAD): The DAD is used to assess functional abilities of activities of daily living (ADL) in individuals with cognitive impairment. This scale has been revised and incorporated into this study by permission of Louise Gauthier, M.Sc., and Dr. Isabelle Gelinas. The DAD is administered to the designated caregiver.

  8. \r\n
\r\n

For each instrument, each assessment is to be performed by the same trained health care professional. If circumstances preclude meeting this requirement, the situation is to be documented on the Clinical Report Form (CRF), and the CRO research physician is to be notified.

\r\n

In addition to the efficacy measures noted above, a survey form will be used to collect information from the caregiver on TTS acceptability (Attachment LZZT.9).

", + "

Group mean changes from baseline in the primary efficacy parameters will serve as efficacy criteria. The ADAS-Cog (11) and the video-referenced CIBIC+ will serve as the primary efficacy instruments. Secondary efficacy instruments will include the DAD, the NPI-X, and the ADAS-Cog (14). The procedures and types of analyses to be done are outlined in Section 4.

\r\n

The primary analysis of efficacy will include only the data obtained up to and including the visit of discontinuation of study drug. Furthermore, the primary analysis will not include efficacy data obtained at any visit where the study drug was not administered in the preceding three days. Analyses that include the retrieved dropouts are considered secondary.

", + "

Blood samples (7 mL) for the determination of xanomeline concentrations in plasma will be collected from each patient at Visits 3, 4, 5, 7, 9, and 11. The blood sample drawn at Visit 3 is a baseline sample. The remaining 5 clinic visits should be scheduled so that 1 blood sample is collected at any time during each of the following intervals: early AM visit (hold application of new patch until after blood sample is collected); 9AM to 11AM; 11AM to 1PM; 1PM to 3PM; and 3PM to 5PM. Collection of blood samples during each of these intervals should not occur in any particular order, nor should they occur in the same order for each patient. Every effort should be made to comply with the suggested sampling times. This blood-sampling schedule is based on a sparse sampling strategy where only a few samples will be collected from each patient. The most crucial aspect of the sampling design is to record the date and exact time the sample was drawn and to record the date and time of patch application on the day of the clinic visit and the previous 2 days.

\r\n

If a patient is discontinued from the study prior to protocol completion, a pharmacokinetic blood sample should be drawn at the early discontinuation visit. The date and exact time the sample was drawn and the date of the last patch application should be recorded.

\r\n

Immediately after collection, each sample will be centrifuged at approximately 177 × G for 15 minutes. The plasma will be transferred into a polypropylene tube bearing the identical label as the blood collection tube. Samples will be capped and frozen at approximately −20°C. Care must be taken to insure that the samples remain frozen during transit.

\r\n

The samples will be shipped on dry ice to Central Laboratory.

", + "

Investigators are responsible for monitoring the safety of patients who have entered this study and for alerting CRO to any event that seems unusual, even if this event may be considered an unanticipated benefit to the patient. See Section 3.9.3.2.1.

\r\n

Investigators must ensure that appropriate medical care is maintained throughout the study and after the trial (for example, to follow adverse events).

", + "

Safety measures will be performed at designated times by recording adverse events, laboratory test results, vital signs (including supine/standing pulse and blood pressure readings) ECG monitoring, and Ambulatory ECGs (see Schedule of Events, Attachment LZZT.1).

", + "

Lilly has standards for reporting adverse events that are to be followed, regardless of applicable regulatory requirements that are less stringent. For purposes of collecting and evaluating all information about Lilly drugs used in clinical trials, an adverse event is defined as any undesirable experience or an unanticipated benefit (see Section 3.9.3.2.1) that occurs after informed consent for the study has been obtained, without regard to treatment group assignment, even if no study medication has been taken. Lack of drug effect is not an adverse event in clinical trials, because the purpose of the clinical trial is to establish drug effect.

\r\n

At the first visit, study site personnel will question the patient and will note the occurrence and nature of presenting condition(s) and of any preexisting condition(s). At subsequent visits, site personnel will again question the patient and will note any change in the presenting condition(s), any change in the preexisting condition(s), and/or the occurrence and nature of any adverse events.

", + "

All adverse events must be reported to CRO via case report form.

\r\n

Study site personnel must report to CRO immediately, by telephone, any serious adverse event (see Section 3.9.3.2.2 below), or if the investigator unblinds a patient's treatment group assignment because of an adverse event or for any other reason.

\r\n

If a patient's dosage is reduced or if a patient is discontinued from the study because of any significant laboratory abnormality, inadequate response to treatment, or any other reason, the circumstances and data leading to any such dosage reduction or discontinuation must be reported and clearly documented by study site personnel on the clinical report form.

\r\n

An event that may be considered an unanticipated benefit to the patient (for example, sleeping longer) should be reported to CRO as an adverse event on the clinical report form. “Unanticipated benefit” is a COSTART classification term. In cases where the investigator notices an unanticipated benefit to the patient, study site personnel should enter the actual term such as “sleeping longer,” and code “unanticipated benefit” in the clinical report form adverse event section.

\r\n

Solicited adverse events from the skin rash questionnaire (see Section 3.9.3.4) should be reported on the questionnaire only and not also on the adverse event clinical report form

", + "

Study site personnel must report to CRO immediately, by telephone, any adverse event from this study that is alarming or that:

\r\n
    \r\n
  • Results in death

  • \r\n
  • Results in initial or prolonged inpatient hospitalization

  • \r\n
  • Is life-threatening

  • \r\n
  • Results in severe or permanent disability

  • \r\n
  • Results in cancer [(other than cancers diagnosed prior to enrollment in studies involving patients with cancer)]

  • \r\n
  • Results in a congenital anomaly

  • \r\n
  • Is a drug overdose

  • \r\n
  • Is significant for any other reason.

  • \r\n
\r\n

Definition of overdose: For a drug under clinical investigation, an overdose is any intentional or unintentional consumption of the drug (by any route) that exceeds the dose recommended in the Clinical Investigator's Brochure or in an investigational protocol, whichever dose is larger. For a marketed drug, a drug overdose is any intentional or unintentional consumption of the drug (by any route) that exceeds the dose listed in product labeling, even if the larger dose is prescribed by a physician.

", + "

Table LZZT.1 lists the clinical laboratory tests that will be performed at Visit 1.

\r\n

Table LZZT.1. Laboratory Tests Performed at Admission (Visit 1)

\r\n

Safety Laboratory Tests

\r\n\r\n\r\n\r\n\r\n\r\n
\r\n

Hematology:

\r\n
    \r\n
  • Hemoglobin
  • \r\n
  • Hematocrit
  • \r\n
  • Erythrocyte count (RBC)
  • \r\n
  • Mean cell volume (MCV)
  • \r\n
  • Mean cell hemoglobin (MCH)
  • \r\n
  • Mean cell hemoglobin concentration (MCHC)
  • \r\n
  • Leukocytes (WBC)
  • \r\n
  • Neutrophils, segmented
  • \r\n
  • Neutrophils, juvenile (bands)
  • \r\n
  • Lymphocytes
  • \r\n
  • Monocytes
  • \r\n
  • Eosinophils
  • \r\n
  • Basophils
  • \r\n
  • Platelet
  • \r\n
  • Cell morphology
  • \r\n
\r\n

Urinalysis:

\r\n
    \r\n
  • Color
  • \r\n
  • Specific gravity
  • \r\n
  • pH
  • \r\n
  • Protein
  • \r\n
  • Glucose
  • \r\n
  • Ketones
  • \r\n
  • Bilirubin
  • \r\n
  • Urobilinogen
  • \r\n
  • Blood
  • \r\n
  • Nitrite
  • \r\n
  • Microscopic examination of sediment
  • \r\n
\r\n
\r\n

Clinical Chemistry - Serum Concentration of:

\r\n
    \r\n
  • Sodium
  • \r\n
  • Potassium
  • \r\n
  • Bicarbonate
  • \r\n
  • Total bilirubin
  • \r\n
  • Alkaline phosphatase (ALP)
  • \r\n
  • Gamma-glutamyl transferase (GGT)
  • \r\n
  • Alanine transaminase (ALT/SGPT)
  • \r\n
  • Aspartate transaminase (AST/SGOT)
  • \r\n
  • Blood urea nitrogen (BUN)
  • \r\n
  • Serum creatinine
  • \r\n
  • Uric acid
  • \r\n
  • Phosphorus
  • \r\n
  • Calcium
  • \r\n
  • Glucose, nonfasting
  • \r\n
  • Total protein
  • \r\n
  • Albumin
  • \r\n
  • Cholesterol
  • \r\n
  • Creatine kinase (CK)
  • \r\n
\r\n

Thyroid Function Test (Visit 1 only):

\r\n
    \r\n
  • Free thyroid index
  • \r\n
  • T3 Uptake
  • \r\n
  • T4
  • \r\n
  • Thyroid-stimulating hormone (TSH)
  • \r\n
\r\n

Other Tests (Visit 1 only):

\r\n
    \r\n
  • Folate
  • \r\n
  • Vitamin B 12
  • \r\n
  • Syphilis screening
  • \r\n
  • Hemoglobin A1C (IDDM patients only)
\r\n
\r\n

Laboratory values that fall outside a clinically accepted reference range or values that differ significantly from previous values must be evaluated and commented on by the investigator by marking CS (for clinically significant) or NCS (for not clinically significant) next to the values. Any clinically significant laboratory values that are outside a clinically acceptable range or differ importantly from a previous value should be further commented on in the clinical report form comments page.

\r\n

Hematology, and clinical chemistry will also be performed at Visits 4, 5, 7, 8, 9, 10, 11, 12, and 13. Patients that experience a rash and/or eosinophilia may have additional hematology samples obtained as described in 3.9.3.4 (Other Safety Measures).

\r\n

Urinalysis will also be performed at Visits 4, 9, and 12. The following criteria have been developed to monitor hepatic function.

\r\n
    \r\n
  • Patients with ALT/SGPT levels >120 IU will be retested weekly.

  • \r\n
  • Patients with ALT/SGPT values >400 IU, or alternatively, an elevated ALT/SGPT accompanied by GGT and/or ALP values >500 IU will be retested within 2 days. The sponsor's clinical research administrator or clinical research physician is to be notified. If the retest value does not decrease by at least 10%, the study drug will be discontinued; additional laboratory tests will be performed until levels return to normal. If the retest value does decrease by 10% or more, the study drug may be continued with monitoring at 3 day intervals until ALT/SGPT values decrease to <400 IU or GGT and/or ALP values decrease to <500 IU. \r\n

", + "
Patients experiencing Rash and/or Eosinophilia\r\n

The administration of placebo and xanomeline TTS is associated with a rash and/or eosinophilia in some patients. The rash is characterized in the following ways:

\r\n
    \r\n
  • The rash is confined to sites of application.

  • \r\n
  • The rash may be associated with pruritus.

  • \r\n
  • In 5% of cases of rash observed in the Interim Analysis, blistering has been observed.

  • \r\n
  • The onset of rash may occur at any time during the course of the study.

  • \r\n
  • A moderate eosinophilia (0.6-1.5 x 103 /microliter) is associated with rash and has been noted in approximately 10% of patients.

  • \r\n
\r\n

It does not appear that the rash constitutes a significant safety risk; however, it could affect the well-being of the patients. The following monitoring is specified:

\r\n

Skin Rash Follow-up

\r\n

For patients who exit the study or its extension with rash at the site(s) of application:

\r\n
    \r\n
  1. Approximately 2 weeks after the last visit, the study site personnel should contact the patient/caregiver by phone and complete the skin rash questionnaire. (Note: those patients with rash who have previously exited the study or its extension should be contacted at earliest convenience.)

  2. \r\n
  3. If caregiver states unequivocally that skin problems have completely resolved, no further follow-up is needed.

  4. \r\n
  5. If caregiver reports scarring and/or other problems, patient should return to clinic for a follow-up visit. The skin rash questionnaire should again be completed. If in the opinion of the investigator, further follow-up is required, contact the CRO medical monitor. Completed skin rash questionnaires should be faxed to CRO.

  6. \r\n
\r\n

Completion of the questionnaires will create a separate data set for solicited adverse events. In completing these forms please note the following:

\r\n
    \r\n
  1. Solicited events (events discovered as result of completion of follow-up questionnaires) should be reported on questionnaire page only.

  2. \r\n
  3. Spontaneously reported adverse events (events presented by the patient without direct questioning of the event) should be reported as described in 3.9.3.2 .1 (Adverse Event Reporting Requirements).

  4. \r\n
\r\n

Serious adverse events should be handled and reported as described in 3.9.3.2.1 without regard to whether the event is solicited or spontaneously reported.

\r\n

Eosinophilia Follow-up

\r\n
    \r\n
  1. For patients that are currently in the study with eosinophil counts greater than 0. 6x10 3 /microliter:

    \r\n
    • Repeat hematology at each visit until resolved in the opinion of the investigator.

  2. \r\n
  3. For patients that are currently in the study with eosinophil counts greater than 1.5x10 3 /microliter:

    \r\n
    • Obtain hematology profile every 2 weeks until resolved or explained by other causes in the opinion of the investigator.

    • \r\n
    • Notify CRO medical monitor.

    • \r\n
  4. \r\n
  5. For patients with eosinophil counts greater than 0.6x10 3 /microliter at exit \r\nfrom the study or its extension:

    \r\n
      \r\n
    • Obtain hematology profile approximately every 2 weeks until resolved or, in the opinion of the investigator, explained by other causes. (Note: patients with eosinophil counts greater than 0.6x10 3 /microliter who have previously exited the study or its extension should return for hematology profile at earliest convenience.)

    • \r\n
  6. \r\n
", + "

Patient should lie supine quietly for at least 5 minutes prior to vital signs measurement. Blood pressure should be measured in the dominant arm with a standardized mercury manometer according to the American Heart Association standard recommendations. Diastolic blood pressure will be measured as the point of disappearance of the Korotkoff sounds (phase V). Heart rate will be measured by auscultation. Patient should then stand up. Blood pressure should again be measured in the dominant arm and heart rate should be measured after approximately 1 and 3 minutes.

\r\n

An automated blood pressure cuff may be used in place of a mercury manometer if it is regularly (at least monthly) standardized against a mercury manometer.

", + "

Cardiovascular status will be assessed during the trial with the following measures:

\r\n
    \r\n
  • All patients will be screened by obtaining a 12-lead ECG, and will have repeat ECGs performed at Visits 4, 5, 7, 8, 9, 10, 11, 12, 13, and early termination (ET) (see Schedule of Events, Attachment LZZT.1).

  • \r\n
  • All patients will undergo a 24-hour Ambulatory ECG at Visit 2 (prior to the initiation of study medication). Although every effort will be made to obtain the entire 24-hour ambulatory ECG recording, this may not always be feasible because of patient behavior or technical difficulties. The minimal recording period for an ambulatory ECG to be considered interpretable will be 8 hours, of which at least 3 hours must be sleep.

  • \r\n
  • The incidence of syncope, defined as an observed loss of consciousness and muscle tone not attributable to transient ischemic attack or to seizure, will be closely monitored. Caregivers will be instructed to report any instance of syncopal episodes to the investigator within 24 hours. The investigator should immediately report such events to the CRO research physician. The CRO research physician will make a clinical assessment of each episode, and with the investigator determine if continuation of \r\ntherapy is appropriate. These findings will be reported to the Lilly research physician immediately.

  • \r\n
", + "

The CRO research physician will monitor safety data throughout the course of the study.

\r\n

Cardiovascular measures, including ECGs and 24-hour Ambulatory ECGs (see Section 3.9.3.4.2) will be monitored on an ongoing basis as follows:

\r\n
    \r\n
  • As noted in Section 3.9.3.4.2, all patients will be screened by obtaining a 12-lead ECG, and will have repeat ECGs performed at Visits 4, 5, 7, 8, 9, 10, 11, 12, 13, and early termination (ET) (see Schedule of Events for Protocol H2Q-MC-LZZT(c), Attachment LZZT.1). ECG data will be interpreted at the site and express mailed overnight to a central facility which will produce a report within 48 hours. The report will be forwarded to the investigator. At screening, the report of the central facility will be used to exclude patients according to criteria specified in Section 3.4.2.2. If, during the treatment phase of the study, review of ECG data (either at the site or at the central facility) reveals left bundle branch block, bradycardia ≤50 beats per minute, sinus pauses >2 seconds, second degree heart block, third degree heart block, Wolff-Parkinson-White syndrome, sustained supraventricular tachyarrhythmia, or ventricular tachycardia at a rate of ≥120 beats per minute lasting ≥10 seconds, the investigator, the Lilly research physician, the CRO research physician, and the cardiologist chairing the DSMB will be notified immediately, and discontinuation of the patient will be considered.

  • \r\n
  • As noted in Section 3.9.3.4.2, all patients will undergo a 24-hour Ambulatory ECG at Visit 2 (prior to the initiation of study medication). Ambulatory ECG data from Visit 2 will be express mailed overnight to a central facility which will produce a report within 24 hours. The report will be forwarded to the investigator. If a report documents sustained ventricular tachycardia with rate >120 beats per minute, third degree heart block, or sinus pauses of >6.0 seconds, the investigator, the Lilly research \r\nphysician, the CRO research physician, and the cardiologist chairing the DSMB will be notified immediately, and the patient will be discontinued. If any report documents sinus pauses of >3.0 seconds or second degree heart block, the CRO research physician, and Lilly research physician, and cardiologist chairing the DSMB will be immediately notified and the record will be reviewed within 24 hours of notification by the cardiologist chairing the DSMB.

  • \r\n
\r\n

In addition to ongoing monitoring of cardiac measures, a comprehensive, periodic review of cardiovascular safety data will be conducted by the DSMB, which will be chaired by an external cardiologist with expertise in arrhythmias, their pharmacological bases, and their clinical implications. The membership of the board will also include two other external cardiologists, a cardiologist from Lilly, a statistician from Lilly, and the Lilly research physician. Only the three external cardiologists will be voting members.

\r\n

After approximately 75 patients have completed 1 month of treatment, the DSMB will meet to decide:

\r\n
    \r\n
  • If discontinuation of the study or any treatment arm is appropriate

  • \r\n
  • If additional cardiovascular monitoring is required

  • \r\n
  • If further cardiovascular monitoring is unnecessary

  • \r\n
  • If adjustment of dose within a treatment arm (or arms) is appropriate.

  • \r\n
\r\n

If necessary, this analysis will be repeated after 150 patients have completed 1 month of treatment, after 225 patients have completed 1 month of treatment, and after 300 patients have completed 1 month of treatment. Primary consideration will be given to the frequency of pauses documented in Ambulatory ECG reports. The number of pauses greater than or equal to 2, 3, 4, 5, and 6 seconds will be tabulated. Primary analysis will focus on the number of pauses greater than or equal to 3 seconds.

\r\n

In the event of a high incidence of patient discontinuation due to syncope, the following guideline may be employed by the DSMB in determining if discontinuation of any treatment arm is appropriate. If the frequency of syncope in a xanomeline treatment arm relative to the frequency of syncope in the placebo arm equals or exceeds the following numbers, then consideration will be given to discontinuing that treatment arm. The Type I error rate for this rule is approximately 0.032 if the incidence in each group is 0.04. The power of this rule is 0.708 if the incidence is 0.04 for placebo and 0.16 for xanomeline TTS.

\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n

Placebo

Xanomeline

PlaceboXanomeline

0

6

615

1

7

716

2

9

817

3

11

918

4

12

1020

5

13

X2X (2-fold)
\r\n

This rule has been used in other studies for monitoring spontaneous events with an incidence of less than 10%. This rule is constructed assuming a 2-group comparison with each group having a final sample size of 100. Unblinding which occurs during these analyses will be at the group level and will be documented.

\r\n

The stopping rule based on Ambulatory ECG findings is as follows:

\r\n

If the number of patients experiencing a pause of ≥6 seconds in a xanomeline treatment arm relative to the number of patients in the placebo arm equals or exceeds the numbers in the following table, then that treatment arm will be discontinued. The Type I error rate for this rule is approximately 0.044 if the incidence in each group is 0.01. The power of this rule is 0.500 if the incidence is 0.01 for placebo and 0.04 for xanomeline TTS.

\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n

Placebo

Xanomeline

0

3

1

5

2

6

3

7

4

8

x

2x

", + "

The medications and efficacy measurements have been used in other studies in elderly subjects and patients.

", + "
", + "

Participation in the study shall be terminated for any patient who is unable or unwilling to comply with the study protocol or who develops a serious adverse event.

\r\n

In addition, patients may be discontinued for any of the following reasons:

\r\n
    \r\n
  • In the opinion of the investigator, a significant adverse event occurs or the \r\nsafety of the patient is otherwise compromised.

  • \r\n
  • The patient requests to be withdrawn from the study.

  • \r\n
  • The physician in charge of the study or Lilly, for any reason stops the \r\npatient's participation in the study.

  • \r\n
\r\n

If a patient's participation terminates early, an early termination visit should be scheduled. Upon decision to discontinue a patient from the study, the patient's dose should be titrated down by instructing the patient to immediately remove the 25-cm2 patch. Patients should be instructed to continue to apply a 50-cm2 patch daily until the early termination visit, at which time the drug will be discontinued. Physical exam, vital signs, temperature, use of concomitant medications, chemistry/hematology/urinalysis labs, xanomeline plasma sample, TTS acceptability survey, efficacy measures, adverse events, and an ECG will be collected at the early termination visit.

\r\n

In the event that a patient's participation or the study itself is terminated, the patient shall return all study drug(s) to the investigator.

", + "

If possible, patients who have terminated early will be retrieved on the date which would have represented Visit 12 (Week 24). Vital signs, temperature, use of concomitant medications, adverse events, and efficacy measure assessment will be gathered at this visit. If the patient is not retrievable, this will be documented in the source record.

", + "

All patients who are enrolled in the study will be included in the efficacy analysis and the safety analysis. Patients will not be excluded from the efficacy analysis for reasons such as non-compliance or ineligibility, except for the time period immediately preceding the efficacy assessment (see Section 3.9.1.2).

", + "

Patients who successfully complete the study will be eligible for participation in an openlabel extension phase, where every patient will be treated with active agent. The patients who elect to participate in the open-label extension phase will be titrated to their maximally titrated dose. This open-label extension phase will continue until the time the product becomes marketed and is available to the public or until the project is discontinued by the sponsor. Patients may terminate at any time at their request.

", + "

Because patients enrolled in this study will be outpatients, the knowledge that patients have taken the medication as prescribed will be assured in the following ways:

\r\n
    \r\n
  1. Investigators will attempt to select those patients and caregivers who \r\nhave been judged to be compliant.

  2. \r\n
  3. Study medication including unused, partially used, and empty patch \r\ncontainers will be returned at each clinical visit so that the remaining \r\nmedication can be counted by authorized investigator staff (nurse, \r\npharmacist, or physician). The number of patches remaining will be \r\nrecorded on the CRF.

  4. \r\n
  5. Following randomization at Visit 3, patients will be instructed to call \r\nthe site if they have difficulty with application or wearing of patches. If \r\ndaily doses are reduced, improperly administered, or if a patch becomes \r\ndetached and requires application of a new patch on three or more days \r\nin any 30-day period, the CRO research physician will be notified.

  6. \r\n
\r\n

If the daily dose is reduced or improperly administered in the 24 hours prior to any scheduled clinic visit, the visit should be rescheduled (except for early termination and retrieval visits).

", + "

To ensure both the safety of participants in the study, and the collection of accurate, complete, and reliable data, Lilly or its representatives will perform the following activities:

\r\n
    \r\n
  • Provide instructional material to the study sites, as appropriate.

  • \r\n
  • Sponsor a start-up training session to instruct the investigators and study \r\ncoordinators. This session will give instruction on the protocol, the \r\ncompletion of the clinical report forms, and study procedures.

  • \r\n
  • Make periodic visits to the study site.

  • \r\n
  • Be available for consultation and stay in contact with the study site \r\npersonnel by mail, telephone, and/or fax.

  • \r\n
  • Review and evaluate clinical report form data and use standard computer \r\nedits to detect errors in data collection.

  • \r\n
\r\n

To ensure the safety of participants in the study and to ensure accurate, complete, and reliable data, the investigator will do the following:

\r\n
    \r\n
  • Keep records of laboratory tests, clinical notes, and patient medical records in the patient files as original source documents for the study.

  • \r\n
\r\n

Lilly or its representatives may periodically check a sample of the patient data recorded against source documents at the study site. The study may be audited by Lilly Medical Quality Assurance (MQA) and/or regulatory agencies at any time. Investigators will be given notice before an MQA audit occurs.

", + "
", + "

In general, all patients will be included in all analyses of efficacy if they have a baseline measurement and at least one postrandomization measurement. Refer to Section 3.9.1.2. for a discussion of which specific efficacy data will be included in the primary analysis.

\r\n

In the event that the doses of xanomeline TTS are changed after the study starts, the analysis will be of three treatment groups (high dose, low dose, and placebo), even though patients within the high dose treatment group, for example, may not all be at exactly the same dose. Also, if the dose is changed midway through the study, the mean dose within each group will be used in the dose response analysis described in Section 4.3.3.

\r\n

All analyses described below will be conducted using the most current production version of SAS® available at the time of analysis.

", + "

All measures (for example, age, gender, origin) obtained at either Visits 1, 2, or 3, prior to randomization, will be summarized by treatment group and across all treatment groups. The groups will be compared by analysis of variance (ANOVA) for continuous variables and by Pearson's chi-square test for categorical variables. Note that because patients are randomized to 1 of the 3 treatment groups, any statistically significant treatment group differences are by definition a Type I error; however, the resulting p-values will be used as another descriptive statistic to help focus possible additional analyses (for example, analysis of covariance, subset analyses) on those factors that are most imbalanced (that is, that have the smallest p-values).

", + "
", + "

Efficacy measures are described in Section 3.9.1.1. As stated in Section 3.9.1.2, the primary outcome measures are the ADAS-Cog (11) and CIBIC+ instruments. Because both of these variables must reach statistical significance, an adjustment to the nominal p-values is necessary in order to maintain a .05 Type I error rate for this study. This adjustment is described in detail in Section 4.3.5.

\r\n

The DAD will be analyzed with respect to the total score, as well as the subscores of \r\ninitiation, planning and organization, and effective performance. This variable is \r\nconsidered a secondary variable in the US, but is a third primary variable in Europe.

\r\n

The NPI-X is a secondary variable. The primary assessment of this instrument will be for the total score, not including the sleep, appetite, and euphoria domains. This total score is computed by taking the product of the frequency and severity scores and summing them up across the domains. Secondary variables derived from the NPI-X include evaluating each domain/behavior separately. Also, caregiver distress from the NPI-X will be analyzed.

\r\n

ADAS-Cog (14) and each of the 14 individual components will also be analyzed. In addition, a subscore of the ADAS-Cog will be computed and analyzed, based on results from a previous large study of oral xanomeline. This subscore, referred to as ADAS-Cog (4), will be the sum of constructional praxis, orientation, spoken language ability, and word finding difficulty in spontaneous speech.

\r\n

Any computed total score will be treated as missing if more than 30% of the items are missing or scored “not applicable”. For example, when computing ADAS-Cog(11), if 4 or more items are missing, then the total score will not be computed. When one or more items are missing (but not more than 30%), the total score will be adjusted in order to maintain the full range of the scale. For example, ADAS-Cog(11) is a 0-70 scale. If the first item, Word Recall (ranges from 0 to 10), is missing, then the remaining 10 items of the ADAS-Cog(11) will be summed and multiplied by (70 / (70-10) ), or 7/6. This computation will occur for all totals and subtotals of ADAS-Cog and NPI-X. DAD is a 40 item questionnaire where each question is scored as either “0” or “1”. The DAD total score and component scores are reported as percentage of items that are scored “1”. So if items of the DAD are “not applicable” or missing, the percentage will be computed for only those items that are scored. As an example, if two items are missing (leaving 38 that are scored), and there are 12 items scored as “1”, the rest as “0”, then the DAD score is 12/38=.316.

", + "

Baseline data will be collected at Visit 3.

\r\n

The primary analysis of ADAS-Cog (11) and CIBIC+ will be the 24-week endpoint, which is defined for each patient and variable as the last measurement obtained postrandomization (prior to protocol defined reduction in dose).

\r\n

Similar analyses at 24 weeks will be conducted for the secondary efficacy variables. Analysis of patients who complete the 24-week study will also be conducted for all efficacy variables; this is referred to as a “completer” analysis.

\r\n

Additionally, each of the efficacy variables will be analyzed at each time point both as “actual cases,” that is, analyzing the data collected at the various time points, and also as a last-observation-carried-forward (LOCF). Note that the LOCF analysis at 24 weeks is the same as the endpoint analysis described previously.

\r\n

Several additional analyses of NPI-X will be conducted. Data from this instrument will be collected every 2 weeks, and represent not the condition of the patient at that moment in time, but rather the worst condition of the patient in the time period since the most recent NPI-X administration. For this reason, the primary analysis of the NPI-X will be of the average of all postrandomization NPI-X subscores except for the one obtained at Week 2. In the event of early discontinuations, those scores that correspond to the interval between Weeks 2 to 24 will be averaged. The reason for excluding Week 2 data from this analysis is that patients could be confused about when a behavior actually stops after randomization; the data obtained at Week 2 could be somewhat “tainted.” Also, by requiring 2 weeks of therapy prior to use of the NPI-X data, the treatment difference should be maximized by giving the drug 2 weeks to work, thereby increasing the statistical power. Secondary analyses of the NPI-X will include the average of all postrandomization weeks, including measures obtained at Weeks 2 and 26.

", + "

The primary method to be used for the primary efficacy variables described in Sections 4.3.1 and 4.3.2 will be analysis of covariance (ANCOVA), except for CIBIC+ which is a score that reflects change from baseline, so there is no corresponding baseline CIBIC+ score. Effects in the ANCOVA model will be the corresponding baseline score, investigator, and treatment. CIBIC+ will be analyzed by analysis of variance (ANOVA), with effects in the model being investigator and treatment. Investigator-by-treatment interaction will be tested in a full model prior to conducting the primary ANCOVA or ANOVA (see description below).

\r\n

Because 3 treatment groups are involved, the primary analysis will be the test for linear dose response in the ANCOVA and ANOVA models described in the preceding paragraph. The result is then a single p-value for each of ADAS-Cog and CIBIC+.

\r\n

Analysis of the secondary efficacy variables will also be ANCOVA. Pairwise treatment comparisons of the adjusted means for all efficacy variables will be conducted using a LSMEANS statement within the GLM procedure.

\r\n

Investigator-by-treatment interaction will be tested in a full ANCOVA or ANOVA model, which takes the models described above, and adds the interaction term to the model. Interaction will be tested at α = .10 level. When the interaction is significant at this level, the data will be examined for each individual investigator to attempt to identify the source of the significant interaction. When the interaction is not significant, this term will be dropped from the model as described above, to test for investigator and treatment main effects. By doing so, all ANCOVA and ANOVA models will be able to validly test for treatment differences without weighting each investigator equally, which is what occurs when using Type III sums of squares (cell means model) with the interaction term present in the model. This equal weighting of investigators can become a serious problem when sample sizes are dramatically different between investigators.

\r\n

For all ANOVA and ANCOVA models, data collected from investigators who enrolled fewer than 3 patients in any one treatment group will be combined prior to analysis. If this combination still results in a treatment group having fewer than 3 patients in any one treatment group, then this group of patients will be combined with the next fewestenrolling investigator. In the event that there is a tie for fewest-enrolling investigator, one of these will be chosen at random by a random-number generator.

\r\n

The inherent assumption of normally distributed data will be evaluated by generating output for the residuals from the full ANCOVA and ANOVA models, which include the interaction term, and by testing for normality using the Shapiro-Wilk test from PROC UNIVARIATE. In the event that the data are predominantly nonnormally distributed, analyses will also be conducted on the ranked data. This rank transformation will be applied by ranking all the data for a particular variable, across all investigators and treatments, from lowest to highest. Integer ranks will be assigned starting at 1; mean ranks will be assigned when ties occur.

\r\n

In addition, the NPI-X will be analyzed in a manner similar to typical analyses of adverse events. In this analysis, each behavior will be considered individually. This analysis is referred to as “treatment-emergent signs and symptoms” (TESS) analysis. For each behavior, the patients will be dichotomized into 1 of 2 groups: those who experienced the behavior for the first time postrandomization, or those who had the quotient between frequency and severity increase relative to the baseline period defines one group. All other patients are in the second group. Treatments will be compared for overall differences by Cochran-Mantel-Haentzel (CMH) test referred to in SAS® as “row mean scores differ,” 2 degrees of freedom. The CMH correlation statistic (1 degree of freedom test), will test for increasing efficacy with increasing dose (trend test).

", + "

All comparisons between xanomeline and placebo with respect to efficacy variables should be one-sided. The justification for this follows.

\r\n

The statistical hypothesis that is tested needs to be consistent with the ultimate data-based decision that is reached. When conducting placebo-controlled trials, it is imperative that the drug be demonstrated to be superior in efficacy to placebo, since equivalent or worse efficacy than placebo will preclude approvability. Consequently, a one-sided test for efficacy is required.

\r\n

The null hypothesis is that the drug is equal or worse than placebo. The alternative hypothesis is that the drug has greater efficacy than placebo. A Type I error occurs only when it is concluded that a study drug is effective when in fact it is not. This can occur in only one tail of the distribution of the treatment difference. Further details of the arguments for one-sided tests in placebo-controlled trials are available in statistical publications (Fisher 1991; Koch 1991; Overall 1991; and Peace 1991).

\r\n

The argument for one-sided tests does not necessarily transfer to safety measures, in general, because one can accept a certain level of toxicity in the presence of strong efficacy. That is, safety is evaluated as part of a benefit/risk ratio.

\r\n

Note that this justification is similar to that used by regulatory agencies worldwide that routinely require one-sided tests for toxicological oncogenicity studies. In that case, the interest is not in whether a drug seems to lessen the occurrence of cancer; the interest is in only one tail of the distribution, namely whether the drug causes cancer to a greater extent than the control.

\r\n

Different regulatory agencies require different type I error rates. Treatment differences that are significant at the .025 α-level will be declared to be “statistically significant.” When a computed p-value falls between .025 and .05, the differences will be described as “marginally statistically significant.” This approach satisfies regulatory agencies who have accepted a one-sided test at the .05 level, and other regulatory agencies who have requested a two-sided test at the .05 level, or equivalently, a one-sided test at the .025 level. In order to facilitate the review of the final study report, two-sided p-values will be presented in addition to the one-sided p-values.

", + "

When there are multiple outcomes, and the study drug is declared to be effective when at least one of these outcomes achieves statistical significance in comparison with a placebo control, a downward adjustment to the nominal α-level is necessary. A well-known simple method is the Bonferroni method, that divides the overall Type I error rate, usually .05, by the number of multiple outcomes. So, for example, if there are two multiple outcomes, the study drug is declared to be effective if at least one of the two outcomes is significant at the .05/2 or .025 level.

\r\n

However, when one has the situation that is present in this study, where there are 2 (or 3 for Europe) outcome variables, each of which must be statistically significant, then the adjustment of the nominal levels is in the opposite direction, that is upwards, in order to maintain an overall Type 1 error rate of .05.

\r\n

In the case of two outcomes, ADAS-Cog (11) and CIBIC+, if the two variables were completely independent, then each variable should be tested at the nominal α-level of .05 1/2 = .2236 level. So if both variables resulted in a nominal p-value less than or equal to .2236, then we would declare the study drug to be effective at the overall Type 1 error rate of .05.

\r\n

We expect these two outcome measures to be correlated. From the first large-scale \r\nefficacy study of oral xanomeline, Study MC-H2Q-LZZA, the correlation between \r\nCIBIC+ and the change in ADAS-Cog(11) from baseline was .252. Consequently, we

\r\n

plan to conduct a randomization test to combine these two dependent dose-response p-values into a single test, which will then be at the .05 Type I error level. Because there will be roughly 300!/(3 * 100!) possible permutations of the data, random data permutations will be sampled (10,000 random permutations).

\r\n

Designate the dose response p-values as p1 and p2 (computed as one-sided p-values), for ADAS-Cog(11) and CIBIC+, respectively. The rejection region is defined as

\r\n

[ {p1 ≤ α and p2 ≤ α} ].

\r\n

The critical value, α, will be determined from the 10,000 random permutations by choosing the value of α to be such that 2.5% of the 10,000 computed pairs of dose response p-values fall in the rejection region. This will correspond to a one-sided test at the .025 level, or equivalently a two-sided test at the .05 level. In addition, by determining the percentage of permuted samples that are more extreme than the observed data, a single p-value is obtained.

", + "

Although safety data is collected at the 24 week visit for retrieved dropouts, these data will not be included in the primary analysis of safety.

\r\n

Pearson's chi-square test will be used to analyze 3 reasons for study discontinuation (protocol completed, lack of efficacy, and adverse event), the incidence of abnormal (high or low) laboratory measures during the postrandomization phase, and the incidence of treatment-emergent adverse events. The analysis of laboratory data is conducted by comparing the measures to the normal reference ranges (based on a large Lilly database), and counting patients in the numerator if they ever had a high (low) value during the postrandomization phase.

\r\n

Additionally, for the continuous laboratory tests, an analysis of change from baseline to endpoint will be conducted using the same ANOVA model described for the efficacy measures in Section 4.3. Because several laboratory analytes are known to be nonnormally distributed (skewed right), these ANOVAs will be conducted on the ranks.

\r\n

Several outcome measures will be extracted and analyzed from the Ambulatory ECG tapes, including number of pauses, QT interval, and AV block (first, second, or third degree). The primary consideration will be the frequency of pauses. The number of pauses greater than or equal to 2, 3, 4, 5 and 6 seconds will be tabulated. Primary analysis will focus on the number of pauses greater than or equal to 3 seconds. Due to possible outliers, these data will be analyzed as the laboratory data, by ANOVA on the ranks.

\r\n

Treatment-emergent adverse events (also referred to as treatment-emergent signs and symptoms, or TESS) are defined as any event reported during the postrandomization period (Weeks 0 - 26) that is worse in severity than during the baseline period, or one that occurs for the first time during the postrandomization period.

", + "

The effect of age, gender, origin, baseline disease severity as measured by MMSE, Apo E, and patient education level upon efficacy will be evaluated if sample sizes are sufficient to warrant such analyses. For example, if all patients are Caucasian, then there is no need to evaluate the co-factor origin. The ANCOVA and ANOVA models described above will be supplemented with terms for the main effect and interaction with treatment. Each co-factor will be analyzed in separate models. The test for treatment-bysubgroup interaction will address whether the response to xanomeline, compared with placebo, is different or consistent between levels of the co-factor.

", + "

Two interim efficacy analyses are planned. The first interim analysis will occur when approximately 50% of the patients have completed 8 weeks; the second interim analysis is to be conducted when approximately 50% of the patients have completed 24 weeks of the study. The purpose of these interim analyses is to provide a rationale for the initiation of subsequent studies of xanomeline TTS, or if the outcome is negative to stop development of xanomeline TTS. The method developed by Enas and Offen (1993) will be used as a guideline as to whether or not to stop one treatment arm, or the study, to declare ineffectiveness. The outcome of the interim analyses will not affect in any way the conduct, results, or analysis of the current study, unless the results are so negative that they lead to a decision to terminate further development of xanomeline TTS in AD. Hence, adjustments to final computed p-values are not appropriate.

\r\n

Planned interim analyses, and any unplanned interim analyses, will be conducted under the auspices of the data monitoring board assigned to this study. Only the data monitoring board is authorized to review completely unblinded interim efficacy and safety analyses and, if necessary, to disseminate those results. The data monitoring board will disseminate interim results only if absolutely necessary. Any such dissemination will be documented and described in the final study report. Study sites will not receive information about interim results unless they need to know for the safety of their patients.

", + "

An analysis of the cardiovascular safety monitoring (see section 3.9.4) will be performed when approximately 25 patients from each treatment arm have completed at least 2 weeks at the treatment arms' respective full dosage (Visit 5). If necessary, this analysis will be repeated every 25 patients per arm. This analysis will be conducted under the auspices of the DSMB. This board membership will be composed of 3 external cardiologists who will be the voting members of the board, a Lilly cardiologist, a Lilly statistician, and the Lilly research physician in charge of the study. Only the DSMB is authorized to review completely unblinded cardiovascular safety analyses and, if necessary, to disseminate those results. The outcome of the cardiovascular safety analyses will determine the need for further Ambulatory ECGs.

", + "

Plasma concentrations of xanomeline will be determined from samples obtained at selected visits (Section 3.9.2). The plasma concentration data for xanomeline, dosing information, and patient characteristics such as weight, gender and origin will be pooled and analyzed using a population pharmacokinetic analysis approach (for example, NONMEM). This approach preserves the individual pharmacokinetic differences through structural and statistical models. The population pharmacokinetic parameters through the structural model, and the interindividual and random residual variability through the components of the statistical models will be estimated. An attempt will also be made to correlate plasma concentrations with efficacy and safety data by means of population pharmacokinetic/pharmacodynamic modeling.

", + "
", + "

In the United States and Canada, the investigator is responsible for preparing the informed consent document. The investigator will use information provided in the current [Clinical Investigator's Brochure or product information] to prepare the informed consent document.

\r\n

The informed consent document will be used to explain in simple terms, before the patient is entered into the study, the risks and benefits to the patient. The informed consent document must contain a statement that the consent is freely given, that the patient is aware of the risks and benefits of entering the study, and that the patient is free to withdraw from the study at any time.

\r\n

As used in this protocol, the term “informed consent” includes all consent and/or assent given by subjects, patients, or their legal representatives.

\r\n

In addition to the elements required by all applicable laws, the 3 numbered paragraphs below must be included in the informed consent document. The language may be altered to match the style of the informed consent document, providing the meaning is unchanged. In some circumstances, local law may require that the text be altered in a way that changes the meaning. These changes can be made only with specific Lilly approval. In these cases, the ethical review board may request from the investigator documentation evidencing Lilly's approval of the language in the informed consent document, which would be different from the language contained in the protocol. Lilly shall, upon request, provide the investigator with such documentation.

\r\n
    \r\n
  1. “I understand that the doctors in charge of this study, or Lilly, may \r\nstop the study or stop my participation in the study at any time, for any \r\nreason, without my consent.”

  2. \r\n
  3. “I hereby give permission for the doctors in charge of this study to \r\nrelease the information regarding, or obtained as a result of, my \r\nparticipation in this study to Lilly, including its agents and contractors; \r\nthe US Food and Drug Administration (FDA) and other governmental \r\nagencies; and to allow them to inspect all my medical records. I \r\nunderstand that medical records that reveal my identity will remain \r\nconfidential, except that they will be provided as noted above or as \r\nmay be required by law.”

  4. \r\n
  5. “If I follow the directions of the doctors in charge of this study and I \r\nam physically injured because of any substance or procedure properly \r\ngiven me under the plan for this study, Lilly will pay the medical \r\nexpenses for the treatment of that injury which are not covered by my \r\nown insurance, by a government program, or by any other third party. \r\nNo other compensation is available from Lilly if any injury occurs.”

  6. \r\n
\r\n

The investigator is responsible for obtaining informed consent from each patient or legal representative and for obtaining the appropriate signatures on the informed consent document prior to the performance of any protocol procedures and prior to the administration of study drug.

", + "

The name and address of the ethical review board are listed on the Investigator/Contacts cover pages provided with this protocol.

\r\n

The investigator will provide Lilly with documentation of ethical review board approval of the protocol and the informed consent document before the study may begin at the site or sites concerned. The ethical review board(s) will review the protocol as required.

\r\n

The investigator must provide the following documentation:

\r\n
  • The ethical review board's annual reapproval of the protocol

  • \r\n
  • The ethical review board's approvals of any revisions to the informed \r\nconsent document or amendments to the protocol.

", + "

This study will be conducted in accordance with the ethical principles stated in the most recent version of the Declaration of Helsinki or the applicable guidelines on good clinical practice, whichever represents the greater protection of the individual.

\r\n

After reading the protocol, each investigator will sign 2 protocol signature pages and return 1 of the signed pages to a Lilly representative (see Attachment LZZT.10).

", + "
\r\n
\r\n
\r\n

Bierer LM, Haroutunian V, Gabriel S, Knott PJ, Carlin LS, Purohit DP, et al. 1995.
Neurochemical correlates of dementia severity in AD: Relative importance of the cholinergic deficits. J of Neurochemistry 64:749-760.

\r\n
\r\n
\r\n
\r\n
\r\n

Cummings JL, Mega M, Gray K, Rosenberg-Thompson S, et al. 1994. The Neuropsychiatric Inventory: Comprehensive assessment of psychopathology in dementia. Neurology 44:2308-2314.

\r\n
\r\n
\r\n
\r\n
\r\n

Enas GG, Offen WW. 1993. A simple stopping rule for declaring treatment ineffectiveness in clinical trials. J Biop Stat 3(1):13-32.

\r\n
\r\n
\r\n
\r\n
\r\n

Fisher A, Barak D. 1994. Promising therapeutic strategies in Alzheimer's disease based \r\non functionally selective M 1 muscarinic agonists. Progress and perspectives in new \r\nmuscarinic agonists. DN&P 7(8):453-464.

\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n

GLUCAGON for Injection ITO [Package Insert]. Osaka, Japan: Kaigen Pharma Co., Ltd; 2016.Available at:\r\n http://www.pmda.go.jp/PmdaSearch/iyakuDetail/ResultDataSetPDF/130616_7229400D1088_\r\n 1_11.

\r\n
\r\n
\r\n
\r\n
\r\n

Polonsky WH, Fisher L, Hessler D, Johnson N. Emotional distress in the partners of type 1diabetes adults:\r\n worries about hypoglycemia and other key concerns. Diabetes Technol Ther. 2016;18:292-297.

\r\n
\r\n
\r\n
\r\n
\r\n

Fisher LD. 1991. The use of one-sided tests in drug trials: an FDA advisory committee \r\nmember's perspective. J Biop Stat 1:151-6.

\r\n
\r\n
\r\n
\r\n
\r\n

Koch GG. 1991. One-sided and two-sided tests and p-values. J Biop Stat 1:161-70.

\r\n
\r\n
\r\n
\r\n
\r\n

Overall JE. 1991. A comment concerning one-sided tests of significance in new drug \r\napplications. J Biop Stat 1:157-60.

\r\n
\r\n
\r\n
\r\n
\r\n

Peace KE. 1991. Oneside or two-sided p-values: which most appropriately address the \r\nquestion of drug efficacy? J Biop Stat 1:133-8.

\r\n
\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The following SoA timelines are auto generated using the detailed study design held within the USDM.

\r\n
\r\n

Timeline: Main Timeline, Potential subject identified

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X1

X

X

X

X

X

X

X

X

X

X

X

X2

X

X

X

X

X3

X

X

X

X

X4

X

X

X

X

X5

X

X

X

X

X

X

X

X

X

X

X

X

X

X

1

Performed if patient is an insulin-dependent diabetic

2

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

3

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

4

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

5

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

Timeline: Adverse Event Timeline, Subject suffers an adverse event

X

Timeline: Early Termination Timeline, Subject terminates the study early

X

", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "

Sponsor Confidentiality Statement:

Full Title:

Trial Acronym:

Protocol Identifier:

Original Protocol:

Version Number:

Version Date:

Amendment Identifier:

Amendment Scope:

Compound Codes(s):

Compound Name(s):

Trial Phase:

Short Title:

Sponsor Name and Address:

,

Regulatory Agency Identifier Number(s):

Spondor Approval Date:

", + "
Committees\r\n

A Data Safety Monitoring Board (DSMB), chaired by an external cardiologist, will meet after 75, 150, 225, and 300 patients have completed 1 month of treatment. The DSMB will review cardiovascular findings to decide if discontinuation of the study or any treatment arm is appropriate, if additional cardiovascular monitoring is required, if further cardiovascular monitoring is unnecessary, or if adjustment of dose within a treatment arm (or arms) is appropriate (see Section 3.9.4).

", + "
\"Alt\r\n

Figure LZZT.1. Illustration of study design for Protocol H2Q-MC-LZZT(c).

\r\n

Following informed consent, patients will be screened at Visit 1. At screening, patients will undergo complete neuropsychiatric assessment, psychometric testing, and general medical assessment (including medical history, pre-existing conditions, physical examination). In addition, vital signs, temperature, medication history, electrocardiogram (ECG), chest x-ray, and safety laboratories will be obtained. During the screening visit, patients will wear a placebo TTS to determine willingness and ability to comply with transdermal administration procedures. If patients have not had central nervous system (CNS) imaging in the previous 12 months, a computed tomography (CT) or magnetic resonance imaging (MRI) scan will be obtained. If patients are insulin dependent diabetics, a hemoglobin A 1c will be obtained. Screening exams and procedures may be performed after Visit 1; however, their results must be completed and available prior to randomization. The screening process should occur within 2 weeks of randomization (Visit 3 of the study).

\r\n

Patients who meet enrollment criteria from Visit 1 will proceed to Visit 2 at which time they will undergo a 24-hour Ambulatory ECG. At Visit 3 the Ambulatory ECG will be removed and patients will be randomized to 1 of 3 treatment arms. The treatment arms will include a placebo arm, a low-dose xanomeline arm (50 cm 2 TTS Formulation E, 54 mg xanomeline), and a high-dose xanomeline arm (75 cm 2 TTS Formulation E, 81 mg xanomeline). All patients receiving xanomeline will be started at 50 cm 2 TTS Formulation E. For the first 8 weeks of treatment, patients will be assessed at clinic visits every 2 weeks and, thereafter, at clinic visits every 4 weeks. Patients who discontinue prior to Visit 12 (Week 24) will be brought back for full efficacy assessments at or near to 24 weeks, whenever possible.

\r\n

At Visits 3, 8, 10, and 12, efficacy instruments (ADAS-Cog, CIBIC+, and DAD) will be administered. NPI-X will be administered at 2-week intervals either at clinic visits or via a telephone interview. Vital signs, temperature, and an assessment of adverse events will be obtained at all clinic visits. An electrocardiogram (ECG), and chemistry/hematology safety labs will be obtained at Visits 4, 5, 7, 8, 9, 10, 11, 12, and 13. Urinalysis will be done at Visits 4, 9, and 12. Use of concomitant medications will be collected at Visits 3, 4, 5, 7, 8, 9, 10, 11, 12, and 13. Plasma levels of xanomeline and metabolites will be obtained at Visits 3, 4, 5, 7, 9, and 11. At Visits 3, 4, 5, 7, 8, 9, 10, 11, and 12, medications will be dispensed to the patients.

\r\n

Visits 1 through 13 should be scheduled relative to Visit 3 (Week 0 - randomization). Visits 4, 5, 7, 8, and 13 should occur within 3 days of their scheduled date. Visits 9, 10, 11, and 12 should occur within 4 days of their scheduled date. At Visit 13 patients will be given the option to enter the open-label extension phase (see Section 3.10.3. Study Extensions).

", + "
\r\n
\r\n

Note:

\r\n

The following SoA timelines are auto generated using the detailed study design held within the USDM.

\r\n
\r\n

Timeline: Main Timeline, Potential subject identified

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X1

X

X

X

X

X

X

X

X

X

X

X

X2

X

X

X

X

X3

X

X

X

X

X4

X

X

X

X

X5

X

X

X

X

X

X

X

X

X

X

X

X

X

X

1

Performed if patient is an insulin-dependent diabetic

2

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

3

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

4

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

5

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

Timeline: Adverse Event Timeline, Subject suffers an adverse event

X

Timeline: Early Termination Timeline, Subject terminates the study early

X

", + "

The primary objectives of this study are

\r\n
    \r\n
  • \r\n
  • \r\n
", + "

The secondary objectives of this study are

\r\n
    \r\n
  • \r\n
  • \r\n
  • \r\n
  • \r\n
", + "

Approximately 300 patients will be enrolled (see Schedule of Events for Protocol H2Q-MC-LZZT(c), Attachment LZZT.1).

\r\n

Duration

\r\n

SOMETHING HERE

\r\n

Patients with probable mild to moderate AD will be studied in a randomized, double-blind, parallel (3 arm), placebo-controlled trial of 26 weeks duration. The study will be conducted on an outpatient basis.

\r\n

At Visit 1, patients who meet the enrollment criteria of Mini-Mental State Examination (MMSE) score of 10 to 23 (Attachment LZZT.6), Hachinski Ischemia Score ≤4 (Attachment LZZT.8), a physical exam, safety labs, ECG, and urinalysis, will proceed to Visit 2 and Visit 3. At Visit 3, patients whose CNS imaging and other pending labs from Visit 1 satisfy the inclusion criteria (Section 3.4.2.1) will be enrolled in the study. Approximately 300 patients with a diagnosis of probable mild to moderate AD will be enrolled in the study.

", + "

Patients may be included in the study only if they meet all the following criteria:

\r\n
01
02
03
04
05
06
07
08
", + "

Patients will be excluded from the study for any of the following reasons:

\r\n
09
10
11
12
13
14
15
16b
17
18
19
20
21
22
23
24
25
26
27b
28b
29b
30b
31b
" + ], + "instanceType": [ + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem" + ] + } + } + ], + "codelists": [] +} diff --git a/tests/resources/CoreIssue897/Positive_datasets.json b/tests/resources/CoreIssue897/Positive_datasets.json new file mode 100644 index 000000000..4a80b8739 --- /dev/null +++ b/tests/resources/CoreIssue897/Positive_datasets.json @@ -0,0 +1,1439 @@ +{ + "datasets": [ + { + "filename": "NarrativeContentItem.xpt", + "name": "NarrativeContentItem", + "label": "Narrative Content Item", + "domain": "NARRATIVECONTENTITEM", + "variables": [ + { + "name": "parent_entity", + "label": "Parent Entity Name", + "type": "String", + "length": null + }, + { + "name": "parent_id", + "label": "Parent Entity Id", + "type": "String", + "length": null + }, + { + "name": "parent_rel", + "label": "Name of Relationship from Parent Entity", + "type": "String", + "length": null + }, + { + "name": "rel_type", + "label": "Type of Relationship", + "type": "String", + "length": null + }, + { + "name": "id", + "label": "(Narrative Content Item Id)", + "type": "String", + "length": null + }, + { + "name": "name", + "label": "Narrative Content Item Name", + "type": "String", + "length": null + }, + { + "name": "text", + "label": "Narrative Content Item Text", + "type": "String", + "length": null + }, + { + "name": "instanceType", + "label": "(Narrative Content Item Instance Type)", + "type": "String", + "length": null + } + ], + "records": { + "parent_entity": [ + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "StudyVersion", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent", + "NarrativeContent" + ], + "parent_id": [ + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "StudyVersion_1", + "NarrativeContent_1", + "NarrativeContent_2", + "NarrativeContent_3", + "NarrativeContent_4", + "NarrativeContent_5", + "NarrativeContent_6", + "NarrativeContent_7", + "NarrativeContent_8", + "NarrativeContent_9", + "NarrativeContent_10", + "NarrativeContent_11", + "NarrativeContent_12", + "NarrativeContent_13", + "NarrativeContent_14", + "NarrativeContent_15", + "NarrativeContent_16", + "NarrativeContent_17", + "NarrativeContent_18", + "NarrativeContent_19", + "NarrativeContent_20", + "NarrativeContent_21", + "NarrativeContent_22", + "NarrativeContent_23", + "NarrativeContent_24", + "NarrativeContent_25", + "NarrativeContent_26", + "NarrativeContent_27", + "NarrativeContent_28", + "NarrativeContent_29", + "NarrativeContent_30", + "NarrativeContent_31", + "NarrativeContent_32", + "NarrativeContent_33", + "NarrativeContent_34", + "NarrativeContent_35", + "NarrativeContent_36", + "NarrativeContent_37", + "NarrativeContent_38", + "NarrativeContent_39", + "NarrativeContent_40", + "NarrativeContent_41", + "NarrativeContent_42", + "NarrativeContent_43", + "NarrativeContent_44", + "NarrativeContent_45", + "NarrativeContent_46", + "NarrativeContent_47", + "NarrativeContent_48", + "NarrativeContent_49", + "NarrativeContent_50", + "NarrativeContent_51", + "NarrativeContent_52", + "NarrativeContent_53", + "NarrativeContent_54", + "NarrativeContent_55", + "NarrativeContent_56", + "NarrativeContent_57", + "NarrativeContent_58", + "NarrativeContent_59", + "NarrativeContent_60", + "NarrativeContent_61", + "NarrativeContent_62", + "NarrativeContent_63", + "NarrativeContent_64", + "NarrativeContent_65", + "NarrativeContent_66", + "NarrativeContent_67", + "NarrativeContent_68", + "NarrativeContent_69", + "NarrativeContent_70", + "NarrativeContent_71", + "NarrativeContent_72", + "NarrativeContent_73", + "NarrativeContent_74", + "NarrativeContent_75", + "NarrativeContent_76", + "NarrativeContent_77", + "NarrativeContent_81", + "NarrativeContent_82", + "NarrativeContent_83", + "NarrativeContent_91", + "NarrativeContent_93", + "NarrativeContent_96", + "NarrativeContent_111", + "NarrativeContent_112" + ], + "parent_rel": [ + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "narrativeContentItems", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId", + "contentItemId" + ], + "rel_type": [ + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "definition", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference", + "reference" + ], + "id": [ + "NarrativeContentItem_1", + "NarrativeContentItem_2", + "NarrativeContentItem_3", + "NarrativeContentItem_4", + "NarrativeContentItem_5", + "NarrativeContentItem_6", + "NarrativeContentItem_7", + "NarrativeContentItem_8", + "NarrativeContentItem_9", + "NarrativeContentItem_10", + "NarrativeContentItem_11", + "NarrativeContentItem_12", + "NarrativeContentItem_13", + "NarrativeContentItem_14", + "NarrativeContentItem_15", + "NarrativeContentItem_16", + "NarrativeContentItem_17", + "NarrativeContentItem_18", + "NarrativeContentItem_19", + "NarrativeContentItem_20", + "NarrativeContentItem_21", + "NarrativeContentItem_22", + "NarrativeContentItem_23", + "NarrativeContentItem_24", + "NarrativeContentItem_25", + "NarrativeContentItem_26", + "NarrativeContentItem_27", + "NarrativeContentItem_28", + "NarrativeContentItem_29", + "NarrativeContentItem_30", + "NarrativeContentItem_31", + "NarrativeContentItem_32", + "NarrativeContentItem_33", + "NarrativeContentItem_34", + "NarrativeContentItem_35", + "NarrativeContentItem_36", + "NarrativeContentItem_37", + "NarrativeContentItem_38", + "NarrativeContentItem_39", + "NarrativeContentItem_40", + "NarrativeContentItem_41", + "NarrativeContentItem_42", + "NarrativeContentItem_43", + "NarrativeContentItem_44", + "NarrativeContentItem_45", + "NarrativeContentItem_46", + "NarrativeContentItem_47", + "NarrativeContentItem_48", + "NarrativeContentItem_49", + "NarrativeContentItem_50", + "NarrativeContentItem_51", + "NarrativeContentItem_52", + "NarrativeContentItem_53", + "NarrativeContentItem_54", + "NarrativeContentItem_55", + "NarrativeContentItem_56", + "NarrativeContentItem_57", + "NarrativeContentItem_58", + "NarrativeContentItem_59", + "NarrativeContentItem_60", + "NarrativeContentItem_61", + "NarrativeContentItem_62", + "NarrativeContentItem_63", + "NarrativeContentItem_64", + "NarrativeContentItem_65", + "NarrativeContentItem_66", + "NarrativeContentItem_67", + "NarrativeContentItem_68", + "NarrativeContentItem_69", + "NarrativeContentItem_70", + "NarrativeContentItem_71", + "NarrativeContentItem_72", + "NarrativeContentItem_73", + "NarrativeContentItem_74", + "NarrativeContentItem_75", + "NarrativeContentItem_76", + "NarrativeContentItem_77", + "NarrativeContentItem_78", + "NarrativeContentItem_79", + "NarrativeContentItem_80", + "NarrativeContentItem_81", + "NarrativeContentItem_82", + "NarrativeContentItem_83", + "NarrativeContentItem_84", + "NarrativeContentItem_85", + "NarrativeContentItem_1", + "NarrativeContentItem_2", + "NarrativeContentItem_3", + "NarrativeContentItem_4", + "NarrativeContentItem_5", + "NarrativeContentItem_6", + "NarrativeContentItem_7", + "NarrativeContentItem_8", + "NarrativeContentItem_9", + "NarrativeContentItem_10", + "NarrativeContentItem_11", + "NarrativeContentItem_12", + "NarrativeContentItem_13", + "NarrativeContentItem_14", + "NarrativeContentItem_15", + "NarrativeContentItem_16", + "NarrativeContentItem_17", + "NarrativeContentItem_18", + "NarrativeContentItem_19", + "NarrativeContentItem_20", + "NarrativeContentItem_21", + "NarrativeContentItem_22", + "NarrativeContentItem_23", + "NarrativeContentItem_24", + "NarrativeContentItem_25", + "NarrativeContentItem_26", + "NarrativeContentItem_27", + "NarrativeContentItem_28", + "NarrativeContentItem_29", + "NarrativeContentItem_30", + "NarrativeContentItem_31", + "NarrativeContentItem_32", + "NarrativeContentItem_33", + "NarrativeContentItem_34", + "NarrativeContentItem_35", + "NarrativeContentItem_36", + "NarrativeContentItem_37", + "NarrativeContentItem_38", + "NarrativeContentItem_39", + "NarrativeContentItem_40", + "NarrativeContentItem_41", + "NarrativeContentItem_42", + "NarrativeContentItem_43", + "NarrativeContentItem_44", + "NarrativeContentItem_45", + "NarrativeContentItem_46", + "NarrativeContentItem_47", + "NarrativeContentItem_48", + "NarrativeContentItem_49", + "NarrativeContentItem_50", + "NarrativeContentItem_51", + "NarrativeContentItem_52", + "NarrativeContentItem_53", + "NarrativeContentItem_54", + "NarrativeContentItem_55", + "NarrativeContentItem_56", + "NarrativeContentItem_57", + "NarrativeContentItem_58", + "NarrativeContentItem_59", + "NarrativeContentItem_60", + "NarrativeContentItem_61", + "NarrativeContentItem_62", + "NarrativeContentItem_63", + "NarrativeContentItem_64", + "NarrativeContentItem_65", + "NarrativeContentItem_66", + "NarrativeContentItem_67", + "NarrativeContentItem_68", + "NarrativeContentItem_69", + "NarrativeContentItem_70", + "NarrativeContentItem_71", + "NarrativeContentItem_72", + "NarrativeContentItem_73", + "NarrativeContentItem_74", + "NarrativeContentItem_75", + "NarrativeContentItem_76", + "NarrativeContentItem_77", + "NarrativeContentItem_78", + "NarrativeContentItem_79", + "NarrativeContentItem_80", + "NarrativeContentItem_81", + "NarrativeContentItem_82", + "NarrativeContentItem_83", + "NarrativeContentItem_84", + "NarrativeContentItem_85" + ], + "name": [ + "NCI_1", + "NCI_2", + "NCI_3", + "NCI_4", + "NCI_5", + "NCI_6", + "NCI_7", + "NCI_8", + "NCI_9", + "NCI_10", + "NCI_11", + "NCI_12", + "NCI_13", + "NCI_14", + "NCI_15", + "NCI_16", + "NCI_17", + "NCI_18", + "NCI_19", + "NCI_20", + "NCI_21", + "NCI_22", + "NCI_23", + "NCI_24", + "NCI_25", + "NCI_26", + "NCI_27", + "NCI_28", + "NCI_29", + "NCI_30", + "NCI_31", + "NCI_32", + "NCI_33", + "NCI_34", + "NCI_35", + "NCI_36", + "NCI_37", + "NCI_38", + "NCI_39", + "NCI_40", + "NCI_41", + "NCI_42", + "NCI_43", + "NCI_44", + "NCI_45", + "NCI_46", + "NCI_47", + "NCI_48", + "NCI_49", + "NCI_50", + "NCI_51", + "NCI_52", + "NCI_53", + "NCI_54", + "NCI_55", + "NCI_56", + "NCI_57", + "NCI_58", + "NCI_59", + "NCI_60", + "NCI_61", + "NCI_62", + "NCI_63", + "NCI_64", + "NCI_65", + "NCI_66", + "NCI_67", + "NCI_68", + "NCI_69", + "NCI_70", + "NCI_71", + "NCI_72", + "NCI_73", + "NCI_74", + "NCI_75", + "NCI_76", + "NCI_77", + "NCI_78", + "NCI_79", + "NCI_80", + "NCI_81", + "NCI_82", + "NCI_83", + "NCI_84", + "NCI_85", + "NCI_1", + "NCI_2", + "NCI_3", + "NCI_4", + "NCI_5", + "NCI_6", + "NCI_7", + "NCI_8", + "NCI_9", + "NCI_10", + "NCI_11", + "NCI_12", + "NCI_13", + "NCI_14", + "NCI_15", + "NCI_16", + "NCI_17", + "NCI_18", + "NCI_19", + "NCI_20", + "NCI_21", + "NCI_22", + "NCI_23", + "NCI_24", + "NCI_25", + "NCI_26", + "NCI_27", + "NCI_28", + "NCI_29", + "NCI_30", + "NCI_31", + "NCI_32", + "NCI_33", + "NCI_34", + "NCI_35", + "NCI_36", + "NCI_37", + "NCI_38", + "NCI_39", + "NCI_40", + "NCI_41", + "NCI_42", + "NCI_43", + "NCI_44", + "NCI_45", + "NCI_46", + "NCI_47", + "NCI_48", + "NCI_49", + "NCI_50", + "NCI_51", + "NCI_52", + "NCI_53", + "NCI_54", + "NCI_55", + "NCI_56", + "NCI_57", + "NCI_58", + "NCI_59", + "NCI_60", + "NCI_61", + "NCI_62", + "NCI_63", + "NCI_64", + "NCI_65", + "NCI_66", + "NCI_67", + "NCI_68", + "NCI_69", + "NCI_70", + "NCI_71", + "NCI_72", + "NCI_73", + "NCI_74", + "NCI_75", + "NCI_76", + "NCI_77", + "NCI_78", + "NCI_79", + "NCI_80", + "NCI_81", + "NCI_82", + "NCI_83", + "NCI_84", + "NCI_85" + ], + "text": [ + "
\r\n
\r\n
\r\n

The information contained in this clinical study protocol is

Copyright © 2006 Eli Lilly and Company.

\r\n
\r\n
\r\n
\r\n
\r\n

\r\n
\r\n
\r\n
\r\n
\r\n

\r\n
\r\n
\r\n
\r\n
\r\n

\r\n
\r\n
\r\n
", + "

The M1 muscarinic-cholinergic receptor is 1 of 5 characterized muscarinic-cholinergic receptor subtypes (Fisher and Barak 1994). M1 receptors in the cerebral cortex and hippocampus are, for the most part, preserved in Alzheimer's disease (AD), while the presynaptic neurons projecting to these receptors from the nucleus basalis of Meynert degenerate (Bierer et al. 1995). The presynaptic loss of cholinergic neurons has been correlated to the antimortum cognitive impairment in AD patients, prompting speculation that replacement therapy with cholinomimetics will alleviate the cognitive dysfunction of the disorder (Fisher and Barak 1994).

\r\n

Xanomeline is a novel M1 agonist which has shown high affinity for the M1 receptor subtype (in transfected cells), and substantially less or no affinity for other muscarinic subtypes. Positron emission tomography (PET) studies of 11C-labeled xanomeline in cynomolgus monkeys have suggested that the compound crosses the blood-brain barrier and preferentially binds the striatum and neocortex.

\r\n

Clinical development of an oral formulation of xanomeline for the indication of mild and moderate AD was initiated approximately 4 years ago. A large-scale study of safety and efficacy provided evidence that an oral dosing regimen of 75 mg three times daily (TID) may be associated with enhanced cognition and improved clinical global impression, relative to placebo. As well, a dramatic reduction in psychosis, agitation, and other problematic behaviors, which often complicate the course of the disease, was documented. However, the discontinuation rate associated with this oral dosing regimen was 58.6%, and alternative clinical strategies have been sought to improve tolerance for the compound.

\r\n

To that end, development of a Transdermal Therapeutic System (TTS) has been initiated. Relative to the oral formulation, the transdermal formulation eliminates high concentrations of xanomeline in the gastrointestinal (GI) tract and presystemic (firstpass) metabolism. Three transdermal delivery systems, hereafter referred to as the xanomeline TTS Formulation A, xanomeline TTS Formulation B, and xanomeline TTS formulation E have been manufactured by Lohman Therapy Systems GmbH of Andernach Germany. TTS Formulation A is 27 mg xanomeline freebase in a 25-cm2 matrix. TTS Formulation B is 57.6 mg xanomeline freebase in a 40-cm2 matrix. Formulation E has been produced in 2 patch sizes: 1) 54 mg xanomeline freebase with 0.06 mg Vitamin E USP in a 50-cm2 matrix and 2) 27 mg xanomeline freebase with 0.03 mg Vitamin E USP in a 25-cm2 matrix. For a detailed description of the composition of these formulations please refer to Part II, Section 14 of the Xanomeline (LY246708) Clinical Investigator's Brochure. For characterization of the safety, tolerance, and pharmacokinetics of xanomeline TTS Formulations A, B, and E, please refer to Part II, Sections 7, 8, and 10 of the Xanomeline (LY246708) Clinical Investigator's Brochure. Formulation E will be studied in this protocol, H2Q-MC-LZZT(c).

", + "
", + "

The primary objectives of this study are

\r\n
    \r\n
  • \r\n
  • \r\n
", + "

The secondary objectives of this study are

\r\n
    \r\n
  • \r\n
  • \r\n
  • \r\n
  • \r\n
", + "
", + "

Patients with probable mild to moderate AD will be studied in a randomized, double-blind, parallel (3 arm), placebo-controlled trial of 26 weeks duration. The study will be conducted on an outpatient basis. Approximately 300 patients will be enrolled (see Schedule of Events for Protocol H2Q-MC-LZZT(c), Attachment LZZT.1).

\r\n

Following informed consent, patients will be screened at Visit 1. At screening, patients will undergo complete neuropsychiatric assessment, psychometric testing, and general medical assessment (including medical history, pre-existing conditions, physical examination). In addition, vital signs, temperature, medication history, electrocardiogram (ECG), chest x-ray, and safety laboratories will be obtained. During the screening visit, patients will wear a placebo TTS to determine willingness and ability to comply with transdermal administration procedures. If patients have not had central nervous system (CNS) imaging in the previous 12 months, a computed tomography (CT) or magnetic resonance imaging (MRI) scan will be obtained. If patients are insulin dependent diabetics, a hemoglobin A 1c will be obtained. Screening exams and procedures may be performed after Visit 1; however, their results must be completed and available prior to randomization. The screening process should occur within 2 weeks of randomization (Visit 3 of the study).

\r\n

Patients who meet enrollment criteria from Visit 1 will proceed to Visit 2 at which time they will undergo a 24-hour Ambulatory ECG. At Visit 3 the Ambulatory ECG will be removed and patients will be randomized to 1 of 3 treatment arms. The treatment arms will include a placebo arm, a low-dose xanomeline arm (50 cm 2 TTS Formulation E, 54 mg xanomeline), and a high-dose xanomeline arm (75 cm 2 TTS Formulation E, 81 mg xanomeline). All patients receiving xanomeline will be started at 50 cm 2 TTS Formulation E. For the first 8 weeks of treatment, patients will be assessed at clinic visits every 2 weeks and, thereafter, at clinic visits every 4 weeks. Patients who discontinue prior to Visit 12 (Week 24) will be brought back for full efficacy assessments at or near to 24 weeks, whenever possible.

\r\n

A Data Safety Monitoring Board (DSMB), chaired by an external cardiologist, will meet after 75, 150, 225, and 300 patients have completed 1 month of treatment. The DSMB will review cardiovascular findings to decide if discontinuation of the study or any treatment arm is appropriate, if additional cardiovascular monitoring is required, if further cardiovascular monitoring is unnecessary, or if adjustment of dose within a treatment arm (or arms) is appropriate (see Section 3.9.4).

\r\n

At Visits 3, 8, 10, and 12, efficacy instruments (ADAS-Cog, CIBIC+, and DAD) will be administered. NPI-X will be administered at 2-week intervals either at clinic visits or via a telephone interview. Vital signs, temperature, and an assessment of adverse events will

\r\n

be obtained at all clinic visits. An electrocardiogram (ECG), and chemistry/hematology safety labs will be obtained at Visits 4, 5, 7, 8, 9, 10, 11, 12, and 13. Urinalysis will be done at Visits 4, 9, and 12. Use of concomitant medications will be collected at Visits 3, 4, 5, 7, 8, 9, 10, 11, 12, and 13. Plasma levels of xanomeline and metabolites will be obtained at Visits 3, 4, 5, 7, 9, and 11. At Visits 3, 4, 5, 7, 8, 9, 10, 11, and 12, medications will be dispensed to the patients.

\r\n

Visits 1 through 13 should be scheduled relative to Visit 3 (Week 0 - randomization). Visits 4, 5, 7, 8, and 13 should occur within 3 days of their scheduled date. Visits 9, 10, 11, and 12 should occur within 4 days of their scheduled date. At Visit 13 patients will be given the option to enter the open-label extension phase (see Section 3.10.3. Study Extensions).

\r\n\"Alt\r\n

Figure LZZT.1. Illustration of study design for Protocol H2Q-MC-LZZT(c).

", + "

Previous studies of the oral formulation have shown that xanomeline tartrate may improve behavior and cognition. Effects on behavior are manifest within 2 to 4 weeks of initiation of treatment. The same studies have shown that 8 to 12 weeks are required to demonstrate effects on cognition and clinical global assessment. This study is intended to determine the acute and chronic effects of the TTS formulation in AD; for that reason, the study is of 26 weeks duration. Dosage specification has been made on the basis of tolerance to the xanomeline TTS in a clinical pharmacology study (H2Q-EW-LKAA), and target plasma levels as determined in studies of the oral formulation of xanomeline (H2Q-MC-LZZA).

\r\n

The parallel dosing regimen maximizes the ability to make direct comparisons between the treatment groups. The use of placebo allows for a blinded, thus minimally biased, study. The placebo treatment group is a comparator group for efficacy and safety assessment.

\r\n

Two interim analyses are planned for this study. The first interim analysis will occur when 50% of the patients have completed Visit 8 (8 weeks). If required, the second interim analysis will occur when 50% of the patients have completed Visit 12 (24 weeks). (See Section 4.6, Interim Analyses.)

", + "

The name, title, and institution of the investigator(s) is/are listed on the Investigator/Contacts cover pages provided with this protocol. If the investigator is changed after the study has been approved by an ethical review board, or a regulatory agency, or by Lilly, this addition will not be considered a change to the protocol. However, the Investigator/Contacts cover pages will be updated to provide this information.

", + "

The final report coordinating investigator will sign the final clinical study report for this study, indicating agreement with the analyses, results, and conclusions of the report.

\r\n

The investigator who will serve as the final report coordinating investigator will be an individual that is involved with the design and analysis of the study. This final report coordinating investigator will be named by the sponsor of the study.

", + "
", + "

An Ethical Review Board (ERB) approved informed consent will be signed by the patient (and/or legal representative) and caregiver after the nature of the study is explained.

", + "

For Lilly studies, the following definitions are used:

\r\n
\r\n
Screen
\r\n
\r\n

Screening is the act of determining if an individual meets minimum requirements to become part of a pool of potential candidates for participation in a clinical study.

\r\n

In this study, screening will include asking the candidate preliminary questions (such as age and general health status) and conducting invasive or diagnostic procedures and/or tests (for example, diagnostic psychological tests, x-rays, blood draws). Patients will sign the consent at their screening visit, thereby consenting to undergo the screening procedures and to participate in the study if they qualify.

\r\n
\r\n
\r\n
\r\n
To enter
\r\n
\r\n

Patients entered into the study are those from whom informed consent for the study has been obtained. Adverse events will be reported for each patient who has entered the study, even if the patient is never assigned to a treatment group (enrolled).

\r\n
\r\n
\r\n
\r\n
To enroll
\r\n
\r\n

Patients who are enrolled in the study are those who have been assigned to a treatment group. Patients who are entered into the study but fail to meet criteria specified in the protocol for treatment assignment will not be enrolled in the study.

\r\n
\r\n
\r\n

At Visit 1, patients who meet the enrollment criteria of Mini-Mental State Examination (MMSE) score of 10 to 23 (Attachment LZZT.6), Hachinski Ischemia Score ≤4 (Attachment LZZT.8), a physical exam, safety labs, ECG, and urinalysis, will proceed to Visit 2 and Visit 3. At Visit 3, patients whose CNS imaging and other pending labs from Visit 1 satisfy the inclusion criteria (Section 3.4.2.1) will be enrolled in the study. Approximately 300 patients with a diagnosis of probable mild to moderate AD will be enrolled in the study.

", + "

Patients may be included in the study only if they meet all the following criteria:

\r\n
01
02
03
04
05
06
07
08
", + "

Patients will be excluded from the study for any of the following reasons:

\r\n
09
10
11
12
13
14
15
16b
17
18
19
20
21
22
23
24
25
26
27b
28b
29b
30b
31b
", + "

The criteria for enrollment must be followed explicitly. If there is inadvertent enrollment of individuals who do not meet enrollment criteria, these individuals should be discontinued from the study. Such individuals can remain in the study only if there are ethical reasons to have them continue. In these cases, the investigator must obtain approval from the Lilly research physician for the study participant to continue in the study (even if the study is being conducted through a contract research organization).

", + "

Probable AD will be defined clinically by NINCDS/ADRDA guidelines as follows:

\r\n
    \r\n
  • Diagnosis of probable AD as defined by National Institute of Neurological and Communicative Disorders and Stroke (NINCDS) and the Alzheimer's Disease and Related Disorders Association (ADRDA) guidelines.

  • \r\n
  • Mild to moderate severity of AD will be defined by the Mini-Mental State Exam as follows:

  • \r\n
  • Mini-Mental State Examination (MMSE) score of 10 to 23.

  • \r\n
  • The absence of other causes of dementia will be performed by clinical opinion and by the following:

  • \r\n
  • Hachinski Ischemic Scale score of ≤4.

  • \r\n
  • CNS imaging (CT scan or MRI of brain) compatible with AD within past 1 year (see Section 3.4.2.1).

  • \r\n
", + "

Approximately 100 patients will be randomized to each of the 3 treatment groups. Previous experience with the oral formulation of xanomeline suggests that this sample size has 90% power to detect a 3.0 mean treatment difference in ADAS-Cog (p<.05, two-sided), based on a standard deviation of 6.5. Furthermore, this sample size has 80% power to detect a 0.36 mean treatment difference in CIBIC+ (p<.05, two-sided), based on a standard deviation of 0.9.

", + "

Commencing at Visit 1, all patients will be assigned an identification number. This identification number and the patient's three initials must appear on all patient-related documents submitted to Lilly.

\r\n

When qualified for enrollment at Visit 3 the patient will be randomized to 1 of 3 treatment arms.

", + "
", + "
\r\n\r\n\r\n\r\n\r\n\r\n\r\n

Primary Study Material:

Xanomeline

TTS (adhesive patches)

50 cm 2 , 54 mg* 25 cm 2 , 27 mg*

Comparator Material:

Placebo

TTS

Identical in appearance to primary study material

\r\n

*All doses are measured in terms of the xanomeline base.

\r\n

Patches should be stored at controlled room temperature, and all used patches must be handled and disposed of as biohazardous waste.

\r\n

For a detailed description of the composition of these formulations please refer to Part II, Section 14 of the Xanomeline (LY246708) Clinical Investigator's Brochure.

", + "

To test acute tolerance of transdermal formulation, patients will have a TTS (placebo) administered at the start of Visit 1, and removed at the conclusion of Visit 1. The patient's and caregiver's willingness to comply with 26 weeks of transdermal therapy should be elicited, and those patients/caregivers unwilling to comply should be excluded.

\r\n

Upon enrollment at Visit 3, and on the morning of each subsequent day of therapy , xanomeline or placebo will be administered with the application of 2 adhesive patches, one 50 cm2 in area, the other 25 cm2 in area. Each morning, prior to the application of the patches, hydrocortisone cream (1%) should be applied to the skin at the intended site of administration, rubbed in, and allowed to penetrate for approximately 30 minutes. Thereafter, excess cream should be wiped away and the patches applied.

\r\n

The patches are to be worn continuously throughout the day, for a period of approximately 12 to 14 hours, and removed in the evening. After removal of the patches, hydrocortisone cream (1%) should be applied locally to the site of administration.

\r\n

Patches should be applied to a dry, intact, non-hairy area. Applying the patch to a shaved area is not recommended. The application site of the patches should be rotated according to the following schedule:

\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n

Day

Patch Location

Sunday

right or left upper arm

Monday

right or left upper back

Tuesday

right or left lower back (above belt line)

Wednesday

right or left buttocks

Thursday

right or left mid-axillary region

Friday

right or left upper thigh

Saturday

right or left upper chest

\r\n

Patients and caregivers are free to select either the left or right site within the constraints of the rotation schedule noted above. Patches should be applied at approximately the same time each day. For patients who habitually bathe in the morning, the patient should bathe prior to application of new patches. Every effort should be taken to allow for morning administration of the patches. Exceptions allowing administration of TTS patches at night instead of in the morning will be made on a case-by-case basis by the CRO medical monitor. In the event that some adhesive remains on the patient's skin and cannot be removed with normal bathing, a special solution will be provided to remove the adhesive.

\r\n

Following randomization at Visit 3, patients will be instructed to call the site if they have difficulty with application or wearing of patches. In the event that a patch becomes detached, a new patch of the same size should be applied (at earliest convenience) to an area of the dermis adjacent to the detachment site, and the rotation schedule should be resumed the following morning. If needed, the edges of the patch may be secured with a special adhesive tape that will be provided. If daily doses are reduced, improperly administered, or if a patch becomes detached and requires application of a new patch on three or more days in any 30-day period, the CRO research physician will be notified.

\r\n

If the daily dose is reduced or improperly administered in the 24 hours prior to any scheduled clinic visit, the visit should be rescheduled (except for early termination and retrieval visits).

\r\n

Patients must be instructed to return all used and unused study drug to the investigator at each visit for proper disposal and CT reconciliation by the investigator.

", + "

The study will be double-blind. To further preserve the blinding of the study, only a minimum number of Lilly and CRO personnel will see the randomization table and codes before the study is complete.

\r\n

Emergency codes generated by a computer drug-labeling system will be available to the investigator. These codes, which reveal the patients treatment group, may be opened during the study only if the choice of follow-up treatment depends on the patient's therapy assignment.

\r\n

The investigator should make every effort to contact the clinical research physician prior to unblinding a patient's therapy assignment. If a patient's therapy assignment is unblinded, Lilly must be notified immediately by telephone. After the study, the investigator must return all sealed and any opened codes.

", + "

Intermittent use of chloral hydrate, zolpidem, or lorazepam is permitted during this clinical trial as indicated for agitation or sleep. If medication is required for agitation for a period exceeding 1 week, a review of the patient's status should be made in consultation with the CRO research physician. Caregivers and patients should be reminded that these medications should not be taken within 24 hours of a clinic visit (including the enrollment visit), and administration of efficacy measures should be deferred if the patient has been treated with these medications within the previous 24 hours.

\r\n

If an antihistamine is required during the study, Claritin® (loratadine) or Allegra® (fexofenadine hydrochloride) are the preferred agents, but should not be taken within 24 hours of a clinic visit. Intermittent use (per package insert) of antitussives (containing antihistamines or codeine) and select narcotic analgesics (acetaminophen with oxycodone, acetaminophen with codeine) are permitted during the trial. Caregivers and patients should be reminded that antihistamines and narcotics should not be taken within 3 days of a clinic efficacy visit (including enrollment visit). If an H 2 blocker is required during the study, Axid® (nizatidine) will be permitted on a case-by-case basis by the CRO medical monitor. For prostatic hypertrophy, small doses (2 mg per day) of Hytrin® (terazosin) or Cardura® (doxazosin) will be permitted on a case-by-case basis. Please consult the medical monitor. The calcium channel blockers Cardene® (nicardipine),

\r\n

Norvasc® (amlodipine), and DynaCirc® (isradipine) are allowed during the study. If a patient has been treated with any medication within disallowed time periods prior to the clinic visit, efficacy measures should be deferred.

\r\n

Other classes of medications not stated in Exclusion Criteria, Section 3.4.2.2, will be permitted. Patients who require treatment with an excluded medication (Section 3.4.2.2) will be discontinued from the study following consultation with the CRO research physician.

", + "
", + "

See Schedule of Events, Attachment LZZT.1 for the times of the study at which efficacy data will be collected.

", + "

The following measures will be performed in the course of the study. At Visits 3, 8, 10, and 12, ADAS-Cog, CIBIC+, and DAD will be administered. NPI-X will be administered at 2-week intervals either at clinic visits or via a telephone interview. Efficacy measures will also be collected at early termination visits, and at the retrieval visit. The neuropsychological assessment should be performed first; other protocol requirements, such as labs and the physical, should follow.

\r\n
    \r\n
  1. Alzheimer's Disease Assessment Scale - Cognitive Subscale (ADAS-Cog): ADAS-Cog is an established measure of cognitive function in Alzheimer's Disease. This scale has been incorporated into this study by permission of Dr. Richard C. Mohs and the American Journal of Psychiatry and was adapted from an article entitled, “The Alzheimer's Disease Assessment Scale (ADAS),” which was published in the American Journal of Psychiatry, Volume No.141, pages 1356-1364, November, 1984, Copyright 1984.

    \r\n

    The ADAS-Cog (11) and the ADAS-Cog (14): The ADAS-Cog (11) is a standard 11-item instrument used to assess word recall, naming objects, commands, constructional praxis, ideational praxis, orientation, word recognition tasks, spoken language ability, comprehension, word finding difficulty, and recall of test instructions. For the purposes of this study, three items (delayed word recall, attention/visual search task, and maze solution) have been added to the ADAS-Cog (11) to assess the patient's attention and concentration. The 14 item instrument will be referred to as the ADAS-Cog (14). At each efficacy visit, all 14 items will be assessed, and in subsequent data analyses, performance on the ADAS-Cog (14) and performance on the subset ADAS-Cog (11) will be considered.

  2. \r\n
  3. Video-referenced Clinician's Interview-Based Impression of Change (CIBIC+): The CIBIC+ is an assessment of the global clinical status relative to baseline. The CIBIC+ used in this study is derived from the Clinical Global Impression of Change, an instrument in the public domain, developed by the National Institute on Aging Alzheimer's Disease Study Units Program (1 U01 AG10483; Leon Thal, Principal Investigator). The instrument employs semi-structured interviews with the patient and caregiver, to assess mental/cognitive state, behavior, and function. These domains are not individually scored, but rather are aggregated in the assignment of a global numeric score on a 1 to 7 scale (1 = marked improvement; 4 = no change; and 7 = marked worsening).

    \r\n

    The clinician assessing CIBIC+ will have at least one year of experience with the instrument and will remain blinded to all other efficacy and safety measures.

  4. \r\n
  5. Revised Neuropsychiatric Inventory (NPI-X): The NPI-X is an assessment of change in psychopathology in patients with dementia. The NPI-X is administered to the designated caregiver. This instrument has been revised from its original version (Cummings et al. 1994) and incorporated into this study with the permission of Dr. Jeffrey L. Cummings.

  6. \r\n
  7. Disability Assessment for Dementia (DAD): The DAD is used to assess functional abilities of activities of daily living (ADL) in individuals with cognitive impairment. This scale has been revised and incorporated into this study by permission of Louise Gauthier, M.Sc., and Dr. Isabelle Gelinas. The DAD is administered to the designated caregiver.

  8. \r\n
\r\n

For each instrument, each assessment is to be performed by the same trained health care professional. If circumstances preclude meeting this requirement, the situation is to be documented on the Clinical Report Form (CRF), and the CRO research physician is to be notified.

\r\n

In addition to the efficacy measures noted above, a survey form will be used to collect information from the caregiver on TTS acceptability (Attachment LZZT.9).

", + "

Group mean changes from baseline in the primary efficacy parameters will serve as efficacy criteria. The ADAS-Cog (11) and the video-referenced CIBIC+ will serve as the primary efficacy instruments. Secondary efficacy instruments will include the DAD, the NPI-X, and the ADAS-Cog (14). The procedures and types of analyses to be done are outlined in Section 4.

\r\n

The primary analysis of efficacy will include only the data obtained up to and including the visit of discontinuation of study drug. Furthermore, the primary analysis will not include efficacy data obtained at any visit where the study drug was not administered in the preceding three days. Analyses that include the retrieved dropouts are considered secondary.

", + "

Blood samples (7 mL) for the determination of xanomeline concentrations in plasma will be collected from each patient at Visits 3, 4, 5, 7, 9, and 11. The blood sample drawn at Visit 3 is a baseline sample. The remaining 5 clinic visits should be scheduled so that 1 blood sample is collected at any time during each of the following intervals: early AM visit (hold application of new patch until after blood sample is collected); 9AM to 11AM; 11AM to 1PM; 1PM to 3PM; and 3PM to 5PM. Collection of blood samples during each of these intervals should not occur in any particular order, nor should they occur in the same order for each patient. Every effort should be made to comply with the suggested sampling times. This blood-sampling schedule is based on a sparse sampling strategy where only a few samples will be collected from each patient. The most crucial aspect of the sampling design is to record the date and exact time the sample was drawn and to record the date and time of patch application on the day of the clinic visit and the previous 2 days.

\r\n

If a patient is discontinued from the study prior to protocol completion, a pharmacokinetic blood sample should be drawn at the early discontinuation visit. The date and exact time the sample was drawn and the date of the last patch application should be recorded.

\r\n

Immediately after collection, each sample will be centrifuged at approximately 177 × G for 15 minutes. The plasma will be transferred into a polypropylene tube bearing the identical label as the blood collection tube. Samples will be capped and frozen at approximately −20°C. Care must be taken to insure that the samples remain frozen during transit.

\r\n

The samples will be shipped on dry ice to Central Laboratory.

", + "

Investigators are responsible for monitoring the safety of patients who have entered this study and for alerting CRO to any event that seems unusual, even if this event may be considered an unanticipated benefit to the patient. See Section 3.9.3.2.1.

\r\n

Investigators must ensure that appropriate medical care is maintained throughout the study and after the trial (for example, to follow adverse events).

", + "

Safety measures will be performed at designated times by recording adverse events, laboratory test results, vital signs (including supine/standing pulse and blood pressure readings) ECG monitoring, and Ambulatory ECGs (see Schedule of Events, Attachment LZZT.1).

", + "

Lilly has standards for reporting adverse events that are to be followed, regardless of applicable regulatory requirements that are less stringent. For purposes of collecting and evaluating all information about Lilly drugs used in clinical trials, an adverse event is defined as any undesirable experience or an unanticipated benefit (see Section 3.9.3.2.1) that occurs after informed consent for the study has been obtained, without regard to treatment group assignment, even if no study medication has been taken. Lack of drug effect is not an adverse event in clinical trials, because the purpose of the clinical trial is to establish drug effect.

\r\n

At the first visit, study site personnel will question the patient and will note the occurrence and nature of presenting condition(s) and of any preexisting condition(s). At subsequent visits, site personnel will again question the patient and will note any change in the presenting condition(s), any change in the preexisting condition(s), and/or the occurrence and nature of any adverse events.

", + "

All adverse events must be reported to CRO via case report form.

\r\n

Study site personnel must report to CRO immediately, by telephone, any serious adverse event (see Section 3.9.3.2.2 below), or if the investigator unblinds a patient's treatment group assignment because of an adverse event or for any other reason.

\r\n

If a patient's dosage is reduced or if a patient is discontinued from the study because of any significant laboratory abnormality, inadequate response to treatment, or any other reason, the circumstances and data leading to any such dosage reduction or discontinuation must be reported and clearly documented by study site personnel on the clinical report form.

\r\n

An event that may be considered an unanticipated benefit to the patient (for example, sleeping longer) should be reported to CRO as an adverse event on the clinical report form. “Unanticipated benefit” is a COSTART classification term. In cases where the investigator notices an unanticipated benefit to the patient, study site personnel should enter the actual term such as “sleeping longer,” and code “unanticipated benefit” in the clinical report form adverse event section.

\r\n

Solicited adverse events from the skin rash questionnaire (see Section 3.9.3.4) should be reported on the questionnaire only and not also on the adverse event clinical report form

", + "

Study site personnel must report to CRO immediately, by telephone, any adverse event from this study that is alarming or that:

\r\n
    \r\n
  • Results in death

  • \r\n
  • Results in initial or prolonged inpatient hospitalization

  • \r\n
  • Is life-threatening

  • \r\n
  • Results in severe or permanent disability

  • \r\n
  • Results in cancer [(other than cancers diagnosed prior to enrollment in studies involving patients with cancer)]

  • \r\n
  • Results in a congenital anomaly

  • \r\n
  • Is a drug overdose

  • \r\n
  • Is significant for any other reason.

  • \r\n
\r\n

Definition of overdose: For a drug under clinical investigation, an overdose is any intentional or unintentional consumption of the drug (by any route) that exceeds the dose recommended in the Clinical Investigator's Brochure or in an investigational protocol, whichever dose is larger. For a marketed drug, a drug overdose is any intentional or unintentional consumption of the drug (by any route) that exceeds the dose listed in product labeling, even if the larger dose is prescribed by a physician.

", + "

Table LZZT.1 lists the clinical laboratory tests that will be performed at Visit 1.

\r\n

Table LZZT.1. Laboratory Tests Performed at Admission (Visit 1)

\r\n

Safety Laboratory Tests

\r\n\r\n\r\n\r\n\r\n\r\n
\r\n

Hematology:

\r\n
    \r\n
  • Hemoglobin
  • \r\n
  • Hematocrit
  • \r\n
  • Erythrocyte count (RBC)
  • \r\n
  • Mean cell volume (MCV)
  • \r\n
  • Mean cell hemoglobin (MCH)
  • \r\n
  • Mean cell hemoglobin concentration (MCHC)
  • \r\n
  • Leukocytes (WBC)
  • \r\n
  • Neutrophils, segmented
  • \r\n
  • Neutrophils, juvenile (bands)
  • \r\n
  • Lymphocytes
  • \r\n
  • Monocytes
  • \r\n
  • Eosinophils
  • \r\n
  • Basophils
  • \r\n
  • Platelet
  • \r\n
  • Cell morphology
  • \r\n
\r\n

Urinalysis:

\r\n
    \r\n
  • Color
  • \r\n
  • Specific gravity
  • \r\n
  • pH
  • \r\n
  • Protein
  • \r\n
  • Glucose
  • \r\n
  • Ketones
  • \r\n
  • Bilirubin
  • \r\n
  • Urobilinogen
  • \r\n
  • Blood
  • \r\n
  • Nitrite
  • \r\n
  • Microscopic examination of sediment
  • \r\n
\r\n
\r\n

Clinical Chemistry - Serum Concentration of:

\r\n
    \r\n
  • Sodium
  • \r\n
  • Potassium
  • \r\n
  • Bicarbonate
  • \r\n
  • Total bilirubin
  • \r\n
  • Alkaline phosphatase (ALP)
  • \r\n
  • Gamma-glutamyl transferase (GGT)
  • \r\n
  • Alanine transaminase (ALT/SGPT)
  • \r\n
  • Aspartate transaminase (AST/SGOT)
  • \r\n
  • Blood urea nitrogen (BUN)
  • \r\n
  • Serum creatinine
  • \r\n
  • Uric acid
  • \r\n
  • Phosphorus
  • \r\n
  • Calcium
  • \r\n
  • Glucose, nonfasting
  • \r\n
  • Total protein
  • \r\n
  • Albumin
  • \r\n
  • Cholesterol
  • \r\n
  • Creatine kinase (CK)
  • \r\n
\r\n

Thyroid Function Test (Visit 1 only):

\r\n
    \r\n
  • Free thyroid index
  • \r\n
  • T3 Uptake
  • \r\n
  • T4
  • \r\n
  • Thyroid-stimulating hormone (TSH)
  • \r\n
\r\n

Other Tests (Visit 1 only):

\r\n
    \r\n
  • Folate
  • \r\n
  • Vitamin B 12
  • \r\n
  • Syphilis screening
  • \r\n
  • Hemoglobin A1C (IDDM patients only)
\r\n
\r\n

Laboratory values that fall outside a clinically accepted reference range or values that differ significantly from previous values must be evaluated and commented on by the investigator by marking CS (for clinically significant) or NCS (for not clinically significant) next to the values. Any clinically significant laboratory values that are outside a clinically acceptable range or differ importantly from a previous value should be further commented on in the clinical report form comments page.

\r\n

Hematology, and clinical chemistry will also be performed at Visits 4, 5, 7, 8, 9, 10, 11, 12, and 13. Patients that experience a rash and/or eosinophilia may have additional hematology samples obtained as described in 3.9.3.4 (Other Safety Measures).

\r\n

Urinalysis will also be performed at Visits 4, 9, and 12. The following criteria have been developed to monitor hepatic function.

\r\n
    \r\n
  • Patients with ALT/SGPT levels >120 IU will be retested weekly.

  • \r\n
  • Patients with ALT/SGPT values >400 IU, or alternatively, an elevated ALT/SGPT accompanied by GGT and/or ALP values >500 IU will be retested within 2 days. The sponsor's clinical research administrator or clinical research physician is to be notified. If the retest value does not decrease by at least 10%, the study drug will be discontinued; additional laboratory tests will be performed until levels return to normal. If the retest value does decrease by 10% or more, the study drug may be continued with monitoring at 3 day intervals until ALT/SGPT values decrease to <400 IU or GGT and/or ALP values decrease to <500 IU. \r\n

", + "
Patients experiencing Rash and/or Eosinophilia\r\n

The administration of placebo and xanomeline TTS is associated with a rash and/or eosinophilia in some patients. The rash is characterized in the following ways:

\r\n
    \r\n
  • The rash is confined to sites of application.

  • \r\n
  • The rash may be associated with pruritus.

  • \r\n
  • In 5% of cases of rash observed in the Interim Analysis, blistering has been observed.

  • \r\n
  • The onset of rash may occur at any time during the course of the study.

  • \r\n
  • A moderate eosinophilia (0.6-1.5 x 103 /microliter) is associated with rash and has been noted in approximately 10% of patients.

  • \r\n
\r\n

It does not appear that the rash constitutes a significant safety risk; however, it could affect the well-being of the patients. The following monitoring is specified:

\r\n

Skin Rash Follow-up

\r\n

For patients who exit the study or its extension with rash at the site(s) of application:

\r\n
    \r\n
  1. Approximately 2 weeks after the last visit, the study site personnel should contact the patient/caregiver by phone and complete the skin rash questionnaire. (Note: those patients with rash who have previously exited the study or its extension should be contacted at earliest convenience.)

  2. \r\n
  3. If caregiver states unequivocally that skin problems have completely resolved, no further follow-up is needed.

  4. \r\n
  5. If caregiver reports scarring and/or other problems, patient should return to clinic for a follow-up visit. The skin rash questionnaire should again be completed. If in the opinion of the investigator, further follow-up is required, contact the CRO medical monitor. Completed skin rash questionnaires should be faxed to CRO.

  6. \r\n
\r\n

Completion of the questionnaires will create a separate data set for solicited adverse events. In completing these forms please note the following:

\r\n
    \r\n
  1. Solicited events (events discovered as result of completion of follow-up questionnaires) should be reported on questionnaire page only.

  2. \r\n
  3. Spontaneously reported adverse events (events presented by the patient without direct questioning of the event) should be reported as described in 3.9.3.2 .1 (Adverse Event Reporting Requirements).

  4. \r\n
\r\n

Serious adverse events should be handled and reported as described in 3.9.3.2.1 without regard to whether the event is solicited or spontaneously reported.

\r\n

Eosinophilia Follow-up

\r\n
    \r\n
  1. For patients that are currently in the study with eosinophil counts greater than 0. 6x10 3 /microliter:

    \r\n
    • Repeat hematology at each visit until resolved in the opinion of the investigator.

  2. \r\n
  3. For patients that are currently in the study with eosinophil counts greater than 1.5x10 3 /microliter:

    \r\n
    • Obtain hematology profile every 2 weeks until resolved or explained by other causes in the opinion of the investigator.

    • \r\n
    • Notify CRO medical monitor.

    • \r\n
  4. \r\n
  5. For patients with eosinophil counts greater than 0.6x10 3 /microliter at exit \r\nfrom the study or its extension:

    \r\n
      \r\n
    • Obtain hematology profile approximately every 2 weeks until resolved or, in the opinion of the investigator, explained by other causes. (Note: patients with eosinophil counts greater than 0.6x10 3 /microliter who have previously exited the study or its extension should return for hematology profile at earliest convenience.)

    • \r\n
  6. \r\n
", + "

Patient should lie supine quietly for at least 5 minutes prior to vital signs measurement. Blood pressure should be measured in the dominant arm with a standardized mercury manometer according to the American Heart Association standard recommendations. Diastolic blood pressure will be measured as the point of disappearance of the Korotkoff sounds (phase V). Heart rate will be measured by auscultation. Patient should then stand up. Blood pressure should again be measured in the dominant arm and heart rate should be measured after approximately 1 and 3 minutes.

\r\n

An automated blood pressure cuff may be used in place of a mercury manometer if it is regularly (at least monthly) standardized against a mercury manometer.

", + "

Cardiovascular status will be assessed during the trial with the following measures:

\r\n
    \r\n
  • All patients will be screened by obtaining a 12-lead ECG, and will have repeat ECGs performed at Visits 4, 5, 7, 8, 9, 10, 11, 12, 13, and early termination (ET) (see Schedule of Events, Attachment LZZT.1).

  • \r\n
  • All patients will undergo a 24-hour Ambulatory ECG at Visit 2 (prior to the initiation of study medication). Although every effort will be made to obtain the entire 24-hour ambulatory ECG recording, this may not always be feasible because of patient behavior or technical difficulties. The minimal recording period for an ambulatory ECG to be considered interpretable will be 8 hours, of which at least 3 hours must be sleep.

  • \r\n
  • The incidence of syncope, defined as an observed loss of consciousness and muscle tone not attributable to transient ischemic attack or to seizure, will be closely monitored. Caregivers will be instructed to report any instance of syncopal episodes to the investigator within 24 hours. The investigator should immediately report such events to the CRO research physician. The CRO research physician will make a clinical assessment of each episode, and with the investigator determine if continuation of \r\ntherapy is appropriate. These findings will be reported to the Lilly research physician immediately.

  • \r\n
", + "

The CRO research physician will monitor safety data throughout the course of the study.

\r\n

Cardiovascular measures, including ECGs and 24-hour Ambulatory ECGs (see Section 3.9.3.4.2) will be monitored on an ongoing basis as follows:

\r\n
    \r\n
  • As noted in Section 3.9.3.4.2, all patients will be screened by obtaining a 12-lead ECG, and will have repeat ECGs performed at Visits 4, 5, 7, 8, 9, 10, 11, 12, 13, and early termination (ET) (see Schedule of Events for Protocol H2Q-MC-LZZT(c), Attachment LZZT.1). ECG data will be interpreted at the site and express mailed overnight to a central facility which will produce a report within 48 hours. The report will be forwarded to the investigator. At screening, the report of the central facility will be used to exclude patients according to criteria specified in Section 3.4.2.2. If, during the treatment phase of the study, review of ECG data (either at the site or at the central facility) reveals left bundle branch block, bradycardia ≤50 beats per minute, sinus pauses >2 seconds, second degree heart block, third degree heart block, Wolff-Parkinson-White syndrome, sustained supraventricular tachyarrhythmia, or ventricular tachycardia at a rate of ≥120 beats per minute lasting ≥10 seconds, the investigator, the Lilly research physician, the CRO research physician, and the cardiologist chairing the DSMB will be notified immediately, and discontinuation of the patient will be considered.

  • \r\n
  • As noted in Section 3.9.3.4.2, all patients will undergo a 24-hour Ambulatory ECG at Visit 2 (prior to the initiation of study medication). Ambulatory ECG data from Visit 2 will be express mailed overnight to a central facility which will produce a report within 24 hours. The report will be forwarded to the investigator. If a report documents sustained ventricular tachycardia with rate >120 beats per minute, third degree heart block, or sinus pauses of >6.0 seconds, the investigator, the Lilly research \r\nphysician, the CRO research physician, and the cardiologist chairing the DSMB will be notified immediately, and the patient will be discontinued. If any report documents sinus pauses of >3.0 seconds or second degree heart block, the CRO research physician, and Lilly research physician, and cardiologist chairing the DSMB will be immediately notified and the record will be reviewed within 24 hours of notification by the cardiologist chairing the DSMB.

  • \r\n
\r\n

In addition to ongoing monitoring of cardiac measures, a comprehensive, periodic review of cardiovascular safety data will be conducted by the DSMB, which will be chaired by an external cardiologist with expertise in arrhythmias, their pharmacological bases, and their clinical implications. The membership of the board will also include two other external cardiologists, a cardiologist from Lilly, a statistician from Lilly, and the Lilly research physician. Only the three external cardiologists will be voting members.

\r\n

After approximately 75 patients have completed 1 month of treatment, the DSMB will meet to decide:

\r\n
    \r\n
  • If discontinuation of the study or any treatment arm is appropriate

  • \r\n
  • If additional cardiovascular monitoring is required

  • \r\n
  • If further cardiovascular monitoring is unnecessary

  • \r\n
  • If adjustment of dose within a treatment arm (or arms) is appropriate.

  • \r\n
\r\n

If necessary, this analysis will be repeated after 150 patients have completed 1 month of treatment, after 225 patients have completed 1 month of treatment, and after 300 patients have completed 1 month of treatment. Primary consideration will be given to the frequency of pauses documented in Ambulatory ECG reports. The number of pauses greater than or equal to 2, 3, 4, 5, and 6 seconds will be tabulated. Primary analysis will focus on the number of pauses greater than or equal to 3 seconds.

\r\n

In the event of a high incidence of patient discontinuation due to syncope, the following guideline may be employed by the DSMB in determining if discontinuation of any treatment arm is appropriate. If the frequency of syncope in a xanomeline treatment arm relative to the frequency of syncope in the placebo arm equals or exceeds the following numbers, then consideration will be given to discontinuing that treatment arm. The Type I error rate for this rule is approximately 0.032 if the incidence in each group is 0.04. The power of this rule is 0.708 if the incidence is 0.04 for placebo and 0.16 for xanomeline TTS.

\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n

Placebo

Xanomeline

PlaceboXanomeline

0

6

615

1

7

716

2

9

817

3

11

918

4

12

1020

5

13

X2X (2-fold)
\r\n

This rule has been used in other studies for monitoring spontaneous events with an incidence of less than 10%. This rule is constructed assuming a 2-group comparison with each group having a final sample size of 100. Unblinding which occurs during these analyses will be at the group level and will be documented.

\r\n

The stopping rule based on Ambulatory ECG findings is as follows:

\r\n

If the number of patients experiencing a pause of ≥6 seconds in a xanomeline treatment arm relative to the number of patients in the placebo arm equals or exceeds the numbers in the following table, then that treatment arm will be discontinued. The Type I error rate for this rule is approximately 0.044 if the incidence in each group is 0.01. The power of this rule is 0.500 if the incidence is 0.01 for placebo and 0.04 for xanomeline TTS.

\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n

Placebo

Xanomeline

0

3

1

5

2

6

3

7

4

8

x

2x

", + "

The medications and efficacy measurements have been used in other studies in elderly subjects and patients.

", + "
", + "

Participation in the study shall be terminated for any patient who is unable or unwilling to comply with the study protocol or who develops a serious adverse event.

\r\n

In addition, patients may be discontinued for any of the following reasons:

\r\n
    \r\n
  • In the opinion of the investigator, a significant adverse event occurs or the \r\nsafety of the patient is otherwise compromised.

  • \r\n
  • The patient requests to be withdrawn from the study.

  • \r\n
  • The physician in charge of the study or Lilly, for any reason stops the \r\npatient's participation in the study.

  • \r\n
\r\n

If a patient's participation terminates early, an early termination visit should be scheduled. Upon decision to discontinue a patient from the study, the patient's dose should be titrated down by instructing the patient to immediately remove the 25-cm2 patch. Patients should be instructed to continue to apply a 50-cm2 patch daily until the early termination visit, at which time the drug will be discontinued. Physical exam, vital signs, temperature, use of concomitant medications, chemistry/hematology/urinalysis labs, xanomeline plasma sample, TTS acceptability survey, efficacy measures, adverse events, and an ECG will be collected at the early termination visit.

\r\n

In the event that a patient's participation or the study itself is terminated, the patient shall return all study drug(s) to the investigator.

", + "

If possible, patients who have terminated early will be retrieved on the date which would have represented Visit 12 (Week 24). Vital signs, temperature, use of concomitant medications, adverse events, and efficacy measure assessment will be gathered at this visit. If the patient is not retrievable, this will be documented in the source record.

", + "

All patients who are enrolled in the study will be included in the efficacy analysis and the safety analysis. Patients will not be excluded from the efficacy analysis for reasons such as non-compliance or ineligibility, except for the time period immediately preceding the efficacy assessment (see Section 3.9.1.2).

", + "

Patients who successfully complete the study will be eligible for participation in an openlabel extension phase, where every patient will be treated with active agent. The patients who elect to participate in the open-label extension phase will be titrated to their maximally titrated dose. This open-label extension phase will continue until the time the product becomes marketed and is available to the public or until the project is discontinued by the sponsor. Patients may terminate at any time at their request.

", + "

Because patients enrolled in this study will be outpatients, the knowledge that patients have taken the medication as prescribed will be assured in the following ways:

\r\n
    \r\n
  1. Investigators will attempt to select those patients and caregivers who \r\nhave been judged to be compliant.

  2. \r\n
  3. Study medication including unused, partially used, and empty patch \r\ncontainers will be returned at each clinical visit so that the remaining \r\nmedication can be counted by authorized investigator staff (nurse, \r\npharmacist, or physician). The number of patches remaining will be \r\nrecorded on the CRF.

  4. \r\n
  5. Following randomization at Visit 3, patients will be instructed to call \r\nthe site if they have difficulty with application or wearing of patches. If \r\ndaily doses are reduced, improperly administered, or if a patch becomes \r\ndetached and requires application of a new patch on three or more days \r\nin any 30-day period, the CRO research physician will be notified.

  6. \r\n
\r\n

If the daily dose is reduced or improperly administered in the 24 hours prior to any scheduled clinic visit, the visit should be rescheduled (except for early termination and retrieval visits).

", + "

To ensure both the safety of participants in the study, and the collection of accurate, complete, and reliable data, Lilly or its representatives will perform the following activities:

\r\n
    \r\n
  • Provide instructional material to the study sites, as appropriate.

  • \r\n
  • Sponsor a start-up training session to instruct the investigators and study \r\ncoordinators. This session will give instruction on the protocol, the \r\ncompletion of the clinical report forms, and study procedures.

  • \r\n
  • Make periodic visits to the study site.

  • \r\n
  • Be available for consultation and stay in contact with the study site \r\npersonnel by mail, telephone, and/or fax.

  • \r\n
  • Review and evaluate clinical report form data and use standard computer \r\nedits to detect errors in data collection.

  • \r\n
\r\n

To ensure the safety of participants in the study and to ensure accurate, complete, and reliable data, the investigator will do the following:

\r\n
    \r\n
  • Keep records of laboratory tests, clinical notes, and patient medical records in the patient files as original source documents for the study.

  • \r\n
\r\n

Lilly or its representatives may periodically check a sample of the patient data recorded against source documents at the study site. The study may be audited by Lilly Medical Quality Assurance (MQA) and/or regulatory agencies at any time. Investigators will be given notice before an MQA audit occurs.

", + "
", + "

In general, all patients will be included in all analyses of efficacy if they have a baseline measurement and at least one postrandomization measurement. Refer to Section 3.9.1.2. for a discussion of which specific efficacy data will be included in the primary analysis.

\r\n

In the event that the doses of xanomeline TTS are changed after the study starts, the analysis will be of three treatment groups (high dose, low dose, and placebo), even though patients within the high dose treatment group, for example, may not all be at exactly the same dose. Also, if the dose is changed midway through the study, the mean dose within each group will be used in the dose response analysis described in Section 4.3.3.

\r\n

All analyses described below will be conducted using the most current production version of SAS® available at the time of analysis.

", + "

All measures (for example, age, gender, origin) obtained at either Visits 1, 2, or 3, prior to randomization, will be summarized by treatment group and across all treatment groups. The groups will be compared by analysis of variance (ANOVA) for continuous variables and by Pearson's chi-square test for categorical variables. Note that because patients are randomized to 1 of the 3 treatment groups, any statistically significant treatment group differences are by definition a Type I error; however, the resulting p-values will be used as another descriptive statistic to help focus possible additional analyses (for example, analysis of covariance, subset analyses) on those factors that are most imbalanced (that is, that have the smallest p-values).

", + "
", + "

Efficacy measures are described in Section 3.9.1.1. As stated in Section 3.9.1.2, the primary outcome measures are the ADAS-Cog (11) and CIBIC+ instruments. Because both of these variables must reach statistical significance, an adjustment to the nominal p-values is necessary in order to maintain a .05 Type I error rate for this study. This adjustment is described in detail in Section 4.3.5.

\r\n

The DAD will be analyzed with respect to the total score, as well as the subscores of \r\ninitiation, planning and organization, and effective performance. This variable is \r\nconsidered a secondary variable in the US, but is a third primary variable in Europe.

\r\n

The NPI-X is a secondary variable. The primary assessment of this instrument will be for the total score, not including the sleep, appetite, and euphoria domains. This total score is computed by taking the product of the frequency and severity scores and summing them up across the domains. Secondary variables derived from the NPI-X include evaluating each domain/behavior separately. Also, caregiver distress from the NPI-X will be analyzed.

\r\n

ADAS-Cog (14) and each of the 14 individual components will also be analyzed. In addition, a subscore of the ADAS-Cog will be computed and analyzed, based on results from a previous large study of oral xanomeline. This subscore, referred to as ADAS-Cog (4), will be the sum of constructional praxis, orientation, spoken language ability, and word finding difficulty in spontaneous speech.

\r\n

Any computed total score will be treated as missing if more than 30% of the items are missing or scored “not applicable”. For example, when computing ADAS-Cog(11), if 4 or more items are missing, then the total score will not be computed. When one or more items are missing (but not more than 30%), the total score will be adjusted in order to maintain the full range of the scale. For example, ADAS-Cog(11) is a 0-70 scale. If the first item, Word Recall (ranges from 0 to 10), is missing, then the remaining 10 items of the ADAS-Cog(11) will be summed and multiplied by (70 / (70-10) ), or 7/6. This computation will occur for all totals and subtotals of ADAS-Cog and NPI-X. DAD is a 40 item questionnaire where each question is scored as either “0” or “1”. The DAD total score and component scores are reported as percentage of items that are scored “1”. So if items of the DAD are “not applicable” or missing, the percentage will be computed for only those items that are scored. As an example, if two items are missing (leaving 38 that are scored), and there are 12 items scored as “1”, the rest as “0”, then the DAD score is 12/38=.316.

", + "

Baseline data will be collected at Visit 3.

\r\n

The primary analysis of ADAS-Cog (11) and CIBIC+ will be the 24-week endpoint, which is defined for each patient and variable as the last measurement obtained postrandomization (prior to protocol defined reduction in dose).

\r\n

Similar analyses at 24 weeks will be conducted for the secondary efficacy variables. Analysis of patients who complete the 24-week study will also be conducted for all efficacy variables; this is referred to as a “completer” analysis.

\r\n

Additionally, each of the efficacy variables will be analyzed at each time point both as “actual cases,” that is, analyzing the data collected at the various time points, and also as a last-observation-carried-forward (LOCF). Note that the LOCF analysis at 24 weeks is the same as the endpoint analysis described previously.

\r\n

Several additional analyses of NPI-X will be conducted. Data from this instrument will be collected every 2 weeks, and represent not the condition of the patient at that moment in time, but rather the worst condition of the patient in the time period since the most recent NPI-X administration. For this reason, the primary analysis of the NPI-X will be of the average of all postrandomization NPI-X subscores except for the one obtained at Week 2. In the event of early discontinuations, those scores that correspond to the interval between Weeks 2 to 24 will be averaged. The reason for excluding Week 2 data from this analysis is that patients could be confused about when a behavior actually stops after randomization; the data obtained at Week 2 could be somewhat “tainted.” Also, by requiring 2 weeks of therapy prior to use of the NPI-X data, the treatment difference should be maximized by giving the drug 2 weeks to work, thereby increasing the statistical power. Secondary analyses of the NPI-X will include the average of all postrandomization weeks, including measures obtained at Weeks 2 and 26.

", + "

The primary method to be used for the primary efficacy variables described in Sections 4.3.1 and 4.3.2 will be analysis of covariance (ANCOVA), except for CIBIC+ which is a score that reflects change from baseline, so there is no corresponding baseline CIBIC+ score. Effects in the ANCOVA model will be the corresponding baseline score, investigator, and treatment. CIBIC+ will be analyzed by analysis of variance (ANOVA), with effects in the model being investigator and treatment. Investigator-by-treatment interaction will be tested in a full model prior to conducting the primary ANCOVA or ANOVA (see description below).

\r\n

Because 3 treatment groups are involved, the primary analysis will be the test for linear dose response in the ANCOVA and ANOVA models described in the preceding paragraph. The result is then a single p-value for each of ADAS-Cog and CIBIC+.

\r\n

Analysis of the secondary efficacy variables will also be ANCOVA. Pairwise treatment comparisons of the adjusted means for all efficacy variables will be conducted using a LSMEANS statement within the GLM procedure.

\r\n

Investigator-by-treatment interaction will be tested in a full ANCOVA or ANOVA model, which takes the models described above, and adds the interaction term to the model. Interaction will be tested at α = .10 level. When the interaction is significant at this level, the data will be examined for each individual investigator to attempt to identify the source of the significant interaction. When the interaction is not significant, this term will be dropped from the model as described above, to test for investigator and treatment main effects. By doing so, all ANCOVA and ANOVA models will be able to validly test for treatment differences without weighting each investigator equally, which is what occurs when using Type III sums of squares (cell means model) with the interaction term present in the model. This equal weighting of investigators can become a serious problem when sample sizes are dramatically different between investigators.

\r\n

For all ANOVA and ANCOVA models, data collected from investigators who enrolled fewer than 3 patients in any one treatment group will be combined prior to analysis. If this combination still results in a treatment group having fewer than 3 patients in any one treatment group, then this group of patients will be combined with the next fewestenrolling investigator. In the event that there is a tie for fewest-enrolling investigator, one of these will be chosen at random by a random-number generator.

\r\n

The inherent assumption of normally distributed data will be evaluated by generating output for the residuals from the full ANCOVA and ANOVA models, which include the interaction term, and by testing for normality using the Shapiro-Wilk test from PROC UNIVARIATE. In the event that the data are predominantly nonnormally distributed, analyses will also be conducted on the ranked data. This rank transformation will be applied by ranking all the data for a particular variable, across all investigators and treatments, from lowest to highest. Integer ranks will be assigned starting at 1; mean ranks will be assigned when ties occur.

\r\n

In addition, the NPI-X will be analyzed in a manner similar to typical analyses of adverse events. In this analysis, each behavior will be considered individually. This analysis is referred to as “treatment-emergent signs and symptoms” (TESS) analysis. For each behavior, the patients will be dichotomized into 1 of 2 groups: those who experienced the behavior for the first time postrandomization, or those who had the quotient between frequency and severity increase relative to the baseline period defines one group. All other patients are in the second group. Treatments will be compared for overall differences by Cochran-Mantel-Haentzel (CMH) test referred to in SAS® as “row mean scores differ,” 2 degrees of freedom. The CMH correlation statistic (1 degree of freedom test), will test for increasing efficacy with increasing dose (trend test).

", + "

All comparisons between xanomeline and placebo with respect to efficacy variables should be one-sided. The justification for this follows.

\r\n

The statistical hypothesis that is tested needs to be consistent with the ultimate data-based decision that is reached. When conducting placebo-controlled trials, it is imperative that the drug be demonstrated to be superior in efficacy to placebo, since equivalent or worse efficacy than placebo will preclude approvability. Consequently, a one-sided test for efficacy is required.

\r\n

The null hypothesis is that the drug is equal or worse than placebo. The alternative hypothesis is that the drug has greater efficacy than placebo. A Type I error occurs only when it is concluded that a study drug is effective when in fact it is not. This can occur in only one tail of the distribution of the treatment difference. Further details of the arguments for one-sided tests in placebo-controlled trials are available in statistical publications (Fisher 1991; Koch 1991; Overall 1991; and Peace 1991).

\r\n

The argument for one-sided tests does not necessarily transfer to safety measures, in general, because one can accept a certain level of toxicity in the presence of strong efficacy. That is, safety is evaluated as part of a benefit/risk ratio.

\r\n

Note that this justification is similar to that used by regulatory agencies worldwide that routinely require one-sided tests for toxicological oncogenicity studies. In that case, the interest is not in whether a drug seems to lessen the occurrence of cancer; the interest is in only one tail of the distribution, namely whether the drug causes cancer to a greater extent than the control.

\r\n

Different regulatory agencies require different type I error rates. Treatment differences that are significant at the .025 α-level will be declared to be “statistically significant.” When a computed p-value falls between .025 and .05, the differences will be described as “marginally statistically significant.” This approach satisfies regulatory agencies who have accepted a one-sided test at the .05 level, and other regulatory agencies who have requested a two-sided test at the .05 level, or equivalently, a one-sided test at the .025 level. In order to facilitate the review of the final study report, two-sided p-values will be presented in addition to the one-sided p-values.

", + "

When there are multiple outcomes, and the study drug is declared to be effective when at least one of these outcomes achieves statistical significance in comparison with a placebo control, a downward adjustment to the nominal α-level is necessary. A well-known simple method is the Bonferroni method, that divides the overall Type I error rate, usually .05, by the number of multiple outcomes. So, for example, if there are two multiple outcomes, the study drug is declared to be effective if at least one of the two outcomes is significant at the .05/2 or .025 level.

\r\n

However, when one has the situation that is present in this study, where there are 2 (or 3 for Europe) outcome variables, each of which must be statistically significant, then the adjustment of the nominal levels is in the opposite direction, that is upwards, in order to maintain an overall Type 1 error rate of .05.

\r\n

In the case of two outcomes, ADAS-Cog (11) and CIBIC+, if the two variables were completely independent, then each variable should be tested at the nominal α-level of .05 1/2 = .2236 level. So if both variables resulted in a nominal p-value less than or equal to .2236, then we would declare the study drug to be effective at the overall Type 1 error rate of .05.

\r\n

We expect these two outcome measures to be correlated. From the first large-scale \r\nefficacy study of oral xanomeline, Study MC-H2Q-LZZA, the correlation between \r\nCIBIC+ and the change in ADAS-Cog(11) from baseline was .252. Consequently, we

\r\n

plan to conduct a randomization test to combine these two dependent dose-response p-values into a single test, which will then be at the .05 Type I error level. Because there will be roughly 300!/(3 * 100!) possible permutations of the data, random data permutations will be sampled (10,000 random permutations).

\r\n

Designate the dose response p-values as p1 and p2 (computed as one-sided p-values), for ADAS-Cog(11) and CIBIC+, respectively. The rejection region is defined as

\r\n

[ {p1 ≤ α and p2 ≤ α} ].

\r\n

The critical value, α, will be determined from the 10,000 random permutations by choosing the value of α to be such that 2.5% of the 10,000 computed pairs of dose response p-values fall in the rejection region. This will correspond to a one-sided test at the .025 level, or equivalently a two-sided test at the .05 level. In addition, by determining the percentage of permuted samples that are more extreme than the observed data, a single p-value is obtained.

", + "

Although safety data is collected at the 24 week visit for retrieved dropouts, these data will not be included in the primary analysis of safety.

\r\n

Pearson's chi-square test will be used to analyze 3 reasons for study discontinuation (protocol completed, lack of efficacy, and adverse event), the incidence of abnormal (high or low) laboratory measures during the postrandomization phase, and the incidence of treatment-emergent adverse events. The analysis of laboratory data is conducted by comparing the measures to the normal reference ranges (based on a large Lilly database), and counting patients in the numerator if they ever had a high (low) value during the postrandomization phase.

\r\n

Additionally, for the continuous laboratory tests, an analysis of change from baseline to endpoint will be conducted using the same ANOVA model described for the efficacy measures in Section 4.3. Because several laboratory analytes are known to be nonnormally distributed (skewed right), these ANOVAs will be conducted on the ranks.

\r\n

Several outcome measures will be extracted and analyzed from the Ambulatory ECG tapes, including number of pauses, QT interval, and AV block (first, second, or third degree). The primary consideration will be the frequency of pauses. The number of pauses greater than or equal to 2, 3, 4, 5 and 6 seconds will be tabulated. Primary analysis will focus on the number of pauses greater than or equal to 3 seconds. Due to possible outliers, these data will be analyzed as the laboratory data, by ANOVA on the ranks.

\r\n

Treatment-emergent adverse events (also referred to as treatment-emergent signs and symptoms, or TESS) are defined as any event reported during the postrandomization period (Weeks 0 - 26) that is worse in severity than during the baseline period, or one that occurs for the first time during the postrandomization period.

", + "

The effect of age, gender, origin, baseline disease severity as measured by MMSE, Apo E, and patient education level upon efficacy will be evaluated if sample sizes are sufficient to warrant such analyses. For example, if all patients are Caucasian, then there is no need to evaluate the co-factor origin. The ANCOVA and ANOVA models described above will be supplemented with terms for the main effect and interaction with treatment. Each co-factor will be analyzed in separate models. The test for treatment-bysubgroup interaction will address whether the response to xanomeline, compared with placebo, is different or consistent between levels of the co-factor.

", + "

Two interim efficacy analyses are planned. The first interim analysis will occur when approximately 50% of the patients have completed 8 weeks; the second interim analysis is to be conducted when approximately 50% of the patients have completed 24 weeks of the study. The purpose of these interim analyses is to provide a rationale for the initiation of subsequent studies of xanomeline TTS, or if the outcome is negative to stop development of xanomeline TTS. The method developed by Enas and Offen (1993) will be used as a guideline as to whether or not to stop one treatment arm, or the study, to declare ineffectiveness. The outcome of the interim analyses will not affect in any way the conduct, results, or analysis of the current study, unless the results are so negative that they lead to a decision to terminate further development of xanomeline TTS in AD. Hence, adjustments to final computed p-values are not appropriate.

\r\n

Planned interim analyses, and any unplanned interim analyses, will be conducted under the auspices of the data monitoring board assigned to this study. Only the data monitoring board is authorized to review completely unblinded interim efficacy and safety analyses and, if necessary, to disseminate those results. The data monitoring board will disseminate interim results only if absolutely necessary. Any such dissemination will be documented and described in the final study report. Study sites will not receive information about interim results unless they need to know for the safety of their patients.

", + "

An analysis of the cardiovascular safety monitoring (see section 3.9.4) will be performed when approximately 25 patients from each treatment arm have completed at least 2 weeks at the treatment arms' respective full dosage (Visit 5). If necessary, this analysis will be repeated every 25 patients per arm. This analysis will be conducted under the auspices of the DSMB. This board membership will be composed of 3 external cardiologists who will be the voting members of the board, a Lilly cardiologist, a Lilly statistician, and the Lilly research physician in charge of the study. Only the DSMB is authorized to review completely unblinded cardiovascular safety analyses and, if necessary, to disseminate those results. The outcome of the cardiovascular safety analyses will determine the need for further Ambulatory ECGs.

", + "

Plasma concentrations of xanomeline will be determined from samples obtained at selected visits (Section 3.9.2). The plasma concentration data for xanomeline, dosing information, and patient characteristics such as weight, gender and origin will be pooled and analyzed using a population pharmacokinetic analysis approach (for example, NONMEM). This approach preserves the individual pharmacokinetic differences through structural and statistical models. The population pharmacokinetic parameters through the structural model, and the interindividual and random residual variability through the components of the statistical models will be estimated. An attempt will also be made to correlate plasma concentrations with efficacy and safety data by means of population pharmacokinetic/pharmacodynamic modeling.

", + "
", + "

In the United States and Canada, the investigator is responsible for preparing the informed consent document. The investigator will use information provided in the current [Clinical Investigator's Brochure or product information] to prepare the informed consent document.

\r\n

The informed consent document will be used to explain in simple terms, before the patient is entered into the study, the risks and benefits to the patient. The informed consent document must contain a statement that the consent is freely given, that the patient is aware of the risks and benefits of entering the study, and that the patient is free to withdraw from the study at any time.

\r\n

As used in this protocol, the term “informed consent” includes all consent and/or assent given by subjects, patients, or their legal representatives.

\r\n

In addition to the elements required by all applicable laws, the 3 numbered paragraphs below must be included in the informed consent document. The language may be altered to match the style of the informed consent document, providing the meaning is unchanged. In some circumstances, local law may require that the text be altered in a way that changes the meaning. These changes can be made only with specific Lilly approval. In these cases, the ethical review board may request from the investigator documentation evidencing Lilly's approval of the language in the informed consent document, which would be different from the language contained in the protocol. Lilly shall, upon request, provide the investigator with such documentation.

\r\n
    \r\n
  1. “I understand that the doctors in charge of this study, or Lilly, may \r\nstop the study or stop my participation in the study at any time, for any \r\nreason, without my consent.”

  2. \r\n
  3. “I hereby give permission for the doctors in charge of this study to \r\nrelease the information regarding, or obtained as a result of, my \r\nparticipation in this study to Lilly, including its agents and contractors; \r\nthe US Food and Drug Administration (FDA) and other governmental \r\nagencies; and to allow them to inspect all my medical records. I \r\nunderstand that medical records that reveal my identity will remain \r\nconfidential, except that they will be provided as noted above or as \r\nmay be required by law.”

  4. \r\n
  5. “If I follow the directions of the doctors in charge of this study and I \r\nam physically injured because of any substance or procedure properly \r\ngiven me under the plan for this study, Lilly will pay the medical \r\nexpenses for the treatment of that injury which are not covered by my \r\nown insurance, by a government program, or by any other third party. \r\nNo other compensation is available from Lilly if any injury occurs.”

  6. \r\n
\r\n

The investigator is responsible for obtaining informed consent from each patient or legal representative and for obtaining the appropriate signatures on the informed consent document prior to the performance of any protocol procedures and prior to the administration of study drug.

", + "

The name and address of the ethical review board are listed on the Investigator/Contacts cover pages provided with this protocol.

\r\n

The investigator will provide Lilly with documentation of ethical review board approval of the protocol and the informed consent document before the study may begin at the site or sites concerned. The ethical review board(s) will review the protocol as required.

\r\n

The investigator must provide the following documentation:

\r\n
  • The ethical review board's annual reapproval of the protocol

  • \r\n
  • The ethical review board's approvals of any revisions to the informed \r\nconsent document or amendments to the protocol.

", + "

This study will be conducted in accordance with the ethical principles stated in the most recent version of the Declaration of Helsinki or the applicable guidelines on good clinical practice, whichever represents the greater protection of the individual.

\r\n

After reading the protocol, each investigator will sign 2 protocol signature pages and return 1 of the signed pages to a Lilly representative (see Attachment LZZT.10).

", + "
\r\n
\r\n
\r\n

Bierer LM, Haroutunian V, Gabriel S, Knott PJ, Carlin LS, Purohit DP, et al. 1995.
Neurochemical correlates of dementia severity in AD: Relative importance of the cholinergic deficits. J of Neurochemistry 64:749-760.

\r\n
\r\n
\r\n
\r\n
\r\n

Cummings JL, Mega M, Gray K, Rosenberg-Thompson S, et al. 1994. The Neuropsychiatric Inventory: Comprehensive assessment of psychopathology in dementia. Neurology 44:2308-2314.

\r\n
\r\n
\r\n
\r\n
\r\n

Enas GG, Offen WW. 1993. A simple stopping rule for declaring treatment ineffectiveness in clinical trials. J Biop Stat 3(1):13-32.

\r\n
\r\n
\r\n
\r\n
\r\n

Fisher A, Barak D. 1994. Promising therapeutic strategies in Alzheimer's disease based \r\non functionally selective M 1 muscarinic agonists. Progress and perspectives in new \r\nmuscarinic agonists. DN&P 7(8):453-464.

\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n

GLUCAGON for Injection ITO [Package Insert]. Osaka, Japan: Kaigen Pharma Co., Ltd; 2016.Available at:\r\n http://www.pmda.go.jp/PmdaSearch/iyakuDetail/ResultDataSetPDF/130616_7229400D1088_\r\n 1_11.

\r\n
\r\n
\r\n
\r\n
\r\n

Polonsky WH, Fisher L, Hessler D, Johnson N. Emotional distress in the partners of type 1diabetes adults:\r\n worries about hypoglycemia and other key concerns. Diabetes Technol Ther. 2016;18:292-297.

\r\n
\r\n
\r\n
\r\n
\r\n

Fisher LD. 1991. The use of one-sided tests in drug trials: an FDA advisory committee \r\nmember's perspective. J Biop Stat 1:151-6.

\r\n
\r\n
\r\n
\r\n
\r\n

Koch GG. 1991. One-sided and two-sided tests and p-values. J Biop Stat 1:161-70.

\r\n
\r\n
\r\n
\r\n
\r\n

Overall JE. 1991. A comment concerning one-sided tests of significance in new drug \r\napplications. J Biop Stat 1:157-60.

\r\n
\r\n
\r\n
\r\n
\r\n

Peace KE. 1991. Oneside or two-sided p-values: which most appropriately address the \r\nquestion of drug efficacy? J Biop Stat 1:133-8.

\r\n
\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The following SoA timelines are auto generated using the detailed study design held within the USDM.

\r\n
\r\n

Timeline: Main Timeline, Potential subject identified

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X1

X

X

X

X

X

X

X

X

X

X

X

X2

X

X

X

X

X3

X

X

X

X

X4

X

X

X

X

X5

X

X

X

X

X

X

X

X

X

X

X

X

X

X

1

Performed if patient is an insulin-dependent diabetic

2

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

3

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

4

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

5

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

Timeline: Adverse Event Timeline, Subject suffers an adverse event

X

Timeline: Early Termination Timeline, Subject terminates the study early

X

", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "

Sponsor Confidentiality Statement:

Full Title:

Trial Acronym:

Protocol Identifier:

Original Protocol:

Version Number:

Version Date:

Amendment Identifier:

Amendment Scope:

Compound Codes(s):

Compound Name(s):

Trial Phase:

Short Title:

Sponsor Name and Address:

,

Regulatory Agency Identifier Number(s):

Spondor Approval Date:

", + "
Committees\r\n

A Data Safety Monitoring Board (DSMB), chaired by an external cardiologist, will meet after 75, 150, 225, and 300 patients have completed 1 month of treatment. The DSMB will review cardiovascular findings to decide if discontinuation of the study or any treatment arm is appropriate, if additional cardiovascular monitoring is required, if further cardiovascular monitoring is unnecessary, or if adjustment of dose within a treatment arm (or arms) is appropriate (see Section 3.9.4).

", + "
\"Alt\r\n

Figure LZZT.1. Illustration of study design for Protocol H2Q-MC-LZZT(c).

\r\n

Following informed consent, patients will be screened at Visit 1. At screening, patients will undergo complete neuropsychiatric assessment, psychometric testing, and general medical assessment (including medical history, pre-existing conditions, physical examination). In addition, vital signs, temperature, medication history, electrocardiogram (ECG), chest x-ray, and safety laboratories will be obtained. During the screening visit, patients will wear a placebo TTS to determine willingness and ability to comply with transdermal administration procedures. If patients have not had central nervous system (CNS) imaging in the previous 12 months, a computed tomography (CT) or magnetic resonance imaging (MRI) scan will be obtained. If patients are insulin dependent diabetics, a hemoglobin A 1c will be obtained. Screening exams and procedures may be performed after Visit 1; however, their results must be completed and available prior to randomization. The screening process should occur within 2 weeks of randomization (Visit 3 of the study).

\r\n

Patients who meet enrollment criteria from Visit 1 will proceed to Visit 2 at which time they will undergo a 24-hour Ambulatory ECG. At Visit 3 the Ambulatory ECG will be removed and patients will be randomized to 1 of 3 treatment arms. The treatment arms will include a placebo arm, a low-dose xanomeline arm (50 cm 2 TTS Formulation E, 54 mg xanomeline), and a high-dose xanomeline arm (75 cm 2 TTS Formulation E, 81 mg xanomeline). All patients receiving xanomeline will be started at 50 cm 2 TTS Formulation E. For the first 8 weeks of treatment, patients will be assessed at clinic visits every 2 weeks and, thereafter, at clinic visits every 4 weeks. Patients who discontinue prior to Visit 12 (Week 24) will be brought back for full efficacy assessments at or near to 24 weeks, whenever possible.

\r\n

At Visits 3, 8, 10, and 12, efficacy instruments (ADAS-Cog, CIBIC+, and DAD) will be administered. NPI-X will be administered at 2-week intervals either at clinic visits or via a telephone interview. Vital signs, temperature, and an assessment of adverse events will be obtained at all clinic visits. An electrocardiogram (ECG), and chemistry/hematology safety labs will be obtained at Visits 4, 5, 7, 8, 9, 10, 11, 12, and 13. Urinalysis will be done at Visits 4, 9, and 12. Use of concomitant medications will be collected at Visits 3, 4, 5, 7, 8, 9, 10, 11, 12, and 13. Plasma levels of xanomeline and metabolites will be obtained at Visits 3, 4, 5, 7, 9, and 11. At Visits 3, 4, 5, 7, 8, 9, 10, 11, and 12, medications will be dispensed to the patients.

\r\n

Visits 1 through 13 should be scheduled relative to Visit 3 (Week 0 - randomization). Visits 4, 5, 7, 8, and 13 should occur within 3 days of their scheduled date. Visits 9, 10, 11, and 12 should occur within 4 days of their scheduled date. At Visit 13 patients will be given the option to enter the open-label extension phase (see Section 3.10.3. Study Extensions).

", + "
\r\n
\r\n

Note:

\r\n

The following SoA timelines are auto generated using the detailed study design held within the USDM.

\r\n
\r\n

Timeline: Main Timeline, Potential subject identified

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X1

X

X

X

X

X

X

X

X

X

X

X

X2

X

X

X

X

X3

X

X

X

X

X4

X

X

X

X

X5

X

X

X

X

X

X

X

X

X

X

X

X

X

X

1

Performed if patient is an insulin-dependent diabetic

2

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

3

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

4

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

5

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

Timeline: Adverse Event Timeline, Subject suffers an adverse event

X

Timeline: Early Termination Timeline, Subject terminates the study early

X

", + "

The primary objectives of this study are

\r\n
    \r\n
  • \r\n
  • \r\n
", + "

The secondary objectives of this study are

\r\n
    \r\n
  • \r\n
  • \r\n
  • \r\n
  • \r\n
", + "

Approximately 300 patients will be enrolled (see Schedule of Events for Protocol H2Q-MC-LZZT(c), Attachment LZZT.1).

\r\n

Duration

\r\n

SOMETHING HERE

\r\n

Patients with probable mild to moderate AD will be studied in a randomized, double-blind, parallel (3 arm), placebo-controlled trial of 26 weeks duration. The study will be conducted on an outpatient basis.

\r\n

At Visit 1, patients who meet the enrollment criteria of Mini-Mental State Examination (MMSE) score of 10 to 23 (Attachment LZZT.6), Hachinski Ischemia Score ≤4 (Attachment LZZT.8), a physical exam, safety labs, ECG, and urinalysis, will proceed to Visit 2 and Visit 3. At Visit 3, patients whose CNS imaging and other pending labs from Visit 1 satisfy the inclusion criteria (Section 3.4.2.1) will be enrolled in the study. Approximately 300 patients with a diagnosis of probable mild to moderate AD will be enrolled in the study.

", + "

Patients may be included in the study only if they meet all the following criteria:

\r\n
01
02
03
04
05
06
07
08
", + "

Patients will be excluded from the study for any of the following reasons:

\r\n
09
10
11
12
13
14
15
16b
17
18
19
20
21
22
23
24
25
26
27b
28b
29b
30b
31b
", + "
\r\n
\r\n
\r\n

The information contained in this clinical study protocol is

Copyright © 2006 Eli Lilly and Company.

\r\n
\r\n
\r\n
\r\n
\r\n

\r\n
\r\n
\r\n
\r\n
\r\n

\r\n
\r\n
\r\n
\r\n
\r\n

\r\n
\r\n
\r\n
", + "

The M1 muscarinic-cholinergic receptor is 1 of 5 characterized muscarinic-cholinergic receptor subtypes (Fisher and Barak 1994). M1 receptors in the cerebral cortex and hippocampus are, for the most part, preserved in Alzheimer's disease (AD), while the presynaptic neurons projecting to these receptors from the nucleus basalis of Meynert degenerate (Bierer et al. 1995). The presynaptic loss of cholinergic neurons has been correlated to the antimortum cognitive impairment in AD patients, prompting speculation that replacement therapy with cholinomimetics will alleviate the cognitive dysfunction of the disorder (Fisher and Barak 1994).

\r\n

Xanomeline is a novel M1 agonist which has shown high affinity for the M1 receptor subtype (in transfected cells), and substantially less or no affinity for other muscarinic subtypes. Positron emission tomography (PET) studies of 11C-labeled xanomeline in cynomolgus monkeys have suggested that the compound crosses the blood-brain barrier and preferentially binds the striatum and neocortex.

\r\n

Clinical development of an oral formulation of xanomeline for the indication of mild and moderate AD was initiated approximately 4 years ago. A large-scale study of safety and efficacy provided evidence that an oral dosing regimen of 75 mg three times daily (TID) may be associated with enhanced cognition and improved clinical global impression, relative to placebo. As well, a dramatic reduction in psychosis, agitation, and other problematic behaviors, which often complicate the course of the disease, was documented. However, the discontinuation rate associated with this oral dosing regimen was 58.6%, and alternative clinical strategies have been sought to improve tolerance for the compound.

\r\n

To that end, development of a Transdermal Therapeutic System (TTS) has been initiated. Relative to the oral formulation, the transdermal formulation eliminates high concentrations of xanomeline in the gastrointestinal (GI) tract and presystemic (firstpass) metabolism. Three transdermal delivery systems, hereafter referred to as the xanomeline TTS Formulation A, xanomeline TTS Formulation B, and xanomeline TTS formulation E have been manufactured by Lohman Therapy Systems GmbH of Andernach Germany. TTS Formulation A is 27 mg xanomeline freebase in a 25-cm2 matrix. TTS Formulation B is 57.6 mg xanomeline freebase in a 40-cm2 matrix. Formulation E has been produced in 2 patch sizes: 1) 54 mg xanomeline freebase with 0.06 mg Vitamin E USP in a 50-cm2 matrix and 2) 27 mg xanomeline freebase with 0.03 mg Vitamin E USP in a 25-cm2 matrix. For a detailed description of the composition of these formulations please refer to Part II, Section 14 of the Xanomeline (LY246708) Clinical Investigator's Brochure. For characterization of the safety, tolerance, and pharmacokinetics of xanomeline TTS Formulations A, B, and E, please refer to Part II, Sections 7, 8, and 10 of the Xanomeline (LY246708) Clinical Investigator's Brochure. Formulation E will be studied in this protocol, H2Q-MC-LZZT(c).

", + "
", + "

The primary objectives of this study are

\r\n
    \r\n
  • \r\n
  • \r\n
", + "

The secondary objectives of this study are

\r\n
    \r\n
  • \r\n
  • \r\n
  • \r\n
  • \r\n
", + "
", + "

Patients with probable mild to moderate AD will be studied in a randomized, double-blind, parallel (3 arm), placebo-controlled trial of 26 weeks duration. The study will be conducted on an outpatient basis. Approximately 300 patients will be enrolled (see Schedule of Events for Protocol H2Q-MC-LZZT(c), Attachment LZZT.1).

\r\n

Following informed consent, patients will be screened at Visit 1. At screening, patients will undergo complete neuropsychiatric assessment, psychometric testing, and general medical assessment (including medical history, pre-existing conditions, physical examination). In addition, vital signs, temperature, medication history, electrocardiogram (ECG), chest x-ray, and safety laboratories will be obtained. During the screening visit, patients will wear a placebo TTS to determine willingness and ability to comply with transdermal administration procedures. If patients have not had central nervous system (CNS) imaging in the previous 12 months, a computed tomography (CT) or magnetic resonance imaging (MRI) scan will be obtained. If patients are insulin dependent diabetics, a hemoglobin A 1c will be obtained. Screening exams and procedures may be performed after Visit 1; however, their results must be completed and available prior to randomization. The screening process should occur within 2 weeks of randomization (Visit 3 of the study).

\r\n

Patients who meet enrollment criteria from Visit 1 will proceed to Visit 2 at which time they will undergo a 24-hour Ambulatory ECG. At Visit 3 the Ambulatory ECG will be removed and patients will be randomized to 1 of 3 treatment arms. The treatment arms will include a placebo arm, a low-dose xanomeline arm (50 cm 2 TTS Formulation E, 54 mg xanomeline), and a high-dose xanomeline arm (75 cm 2 TTS Formulation E, 81 mg xanomeline). All patients receiving xanomeline will be started at 50 cm 2 TTS Formulation E. For the first 8 weeks of treatment, patients will be assessed at clinic visits every 2 weeks and, thereafter, at clinic visits every 4 weeks. Patients who discontinue prior to Visit 12 (Week 24) will be brought back for full efficacy assessments at or near to 24 weeks, whenever possible.

\r\n

A Data Safety Monitoring Board (DSMB), chaired by an external cardiologist, will meet after 75, 150, 225, and 300 patients have completed 1 month of treatment. The DSMB will review cardiovascular findings to decide if discontinuation of the study or any treatment arm is appropriate, if additional cardiovascular monitoring is required, if further cardiovascular monitoring is unnecessary, or if adjustment of dose within a treatment arm (or arms) is appropriate (see Section 3.9.4).

\r\n

At Visits 3, 8, 10, and 12, efficacy instruments (ADAS-Cog, CIBIC+, and DAD) will be administered. NPI-X will be administered at 2-week intervals either at clinic visits or via a telephone interview. Vital signs, temperature, and an assessment of adverse events will

\r\n

be obtained at all clinic visits. An electrocardiogram (ECG), and chemistry/hematology safety labs will be obtained at Visits 4, 5, 7, 8, 9, 10, 11, 12, and 13. Urinalysis will be done at Visits 4, 9, and 12. Use of concomitant medications will be collected at Visits 3, 4, 5, 7, 8, 9, 10, 11, 12, and 13. Plasma levels of xanomeline and metabolites will be obtained at Visits 3, 4, 5, 7, 9, and 11. At Visits 3, 4, 5, 7, 8, 9, 10, 11, and 12, medications will be dispensed to the patients.

\r\n

Visits 1 through 13 should be scheduled relative to Visit 3 (Week 0 - randomization). Visits 4, 5, 7, 8, and 13 should occur within 3 days of their scheduled date. Visits 9, 10, 11, and 12 should occur within 4 days of their scheduled date. At Visit 13 patients will be given the option to enter the open-label extension phase (see Section 3.10.3. Study Extensions).

\r\n\"Alt\r\n

Figure LZZT.1. Illustration of study design for Protocol H2Q-MC-LZZT(c).

", + "

Previous studies of the oral formulation have shown that xanomeline tartrate may improve behavior and cognition. Effects on behavior are manifest within 2 to 4 weeks of initiation of treatment. The same studies have shown that 8 to 12 weeks are required to demonstrate effects on cognition and clinical global assessment. This study is intended to determine the acute and chronic effects of the TTS formulation in AD; for that reason, the study is of 26 weeks duration. Dosage specification has been made on the basis of tolerance to the xanomeline TTS in a clinical pharmacology study (H2Q-EW-LKAA), and target plasma levels as determined in studies of the oral formulation of xanomeline (H2Q-MC-LZZA).

\r\n

The parallel dosing regimen maximizes the ability to make direct comparisons between the treatment groups. The use of placebo allows for a blinded, thus minimally biased, study. The placebo treatment group is a comparator group for efficacy and safety assessment.

\r\n

Two interim analyses are planned for this study. The first interim analysis will occur when 50% of the patients have completed Visit 8 (8 weeks). If required, the second interim analysis will occur when 50% of the patients have completed Visit 12 (24 weeks). (See Section 4.6, Interim Analyses.)

", + "

The name, title, and institution of the investigator(s) is/are listed on the Investigator/Contacts cover pages provided with this protocol. If the investigator is changed after the study has been approved by an ethical review board, or a regulatory agency, or by Lilly, this addition will not be considered a change to the protocol. However, the Investigator/Contacts cover pages will be updated to provide this information.

", + "

The final report coordinating investigator will sign the final clinical study report for this study, indicating agreement with the analyses, results, and conclusions of the report.

\r\n

The investigator who will serve as the final report coordinating investigator will be an individual that is involved with the design and analysis of the study. This final report coordinating investigator will be named by the sponsor of the study.

", + "
", + "

An Ethical Review Board (ERB) approved informed consent will be signed by the patient (and/or legal representative) and caregiver after the nature of the study is explained.

", + "

For Lilly studies, the following definitions are used:

\r\n
\r\n
Screen
\r\n
\r\n

Screening is the act of determining if an individual meets minimum requirements to become part of a pool of potential candidates for participation in a clinical study.

\r\n

In this study, screening will include asking the candidate preliminary questions (such as age and general health status) and conducting invasive or diagnostic procedures and/or tests (for example, diagnostic psychological tests, x-rays, blood draws). Patients will sign the consent at their screening visit, thereby consenting to undergo the screening procedures and to participate in the study if they qualify.

\r\n
\r\n
\r\n
\r\n
To enter
\r\n
\r\n

Patients entered into the study are those from whom informed consent for the study has been obtained. Adverse events will be reported for each patient who has entered the study, even if the patient is never assigned to a treatment group (enrolled).

\r\n
\r\n
\r\n
\r\n
To enroll
\r\n
\r\n

Patients who are enrolled in the study are those who have been assigned to a treatment group. Patients who are entered into the study but fail to meet criteria specified in the protocol for treatment assignment will not be enrolled in the study.

\r\n
\r\n
\r\n

At Visit 1, patients who meet the enrollment criteria of Mini-Mental State Examination (MMSE) score of 10 to 23 (Attachment LZZT.6), Hachinski Ischemia Score ≤4 (Attachment LZZT.8), a physical exam, safety labs, ECG, and urinalysis, will proceed to Visit 2 and Visit 3. At Visit 3, patients whose CNS imaging and other pending labs from Visit 1 satisfy the inclusion criteria (Section 3.4.2.1) will be enrolled in the study. Approximately 300 patients with a diagnosis of probable mild to moderate AD will be enrolled in the study.

", + "

Patients may be included in the study only if they meet all the following criteria:

\r\n
01
02
03
04
05
06
07
08
", + "

Patients will be excluded from the study for any of the following reasons:

\r\n
09
10
11
12
13
14
15
16b
17
18
19
20
21
22
23
24
25
26
27b
28b
29b
30b
31b
", + "

The criteria for enrollment must be followed explicitly. If there is inadvertent enrollment of individuals who do not meet enrollment criteria, these individuals should be discontinued from the study. Such individuals can remain in the study only if there are ethical reasons to have them continue. In these cases, the investigator must obtain approval from the Lilly research physician for the study participant to continue in the study (even if the study is being conducted through a contract research organization).

", + "

Probable AD will be defined clinically by NINCDS/ADRDA guidelines as follows:

\r\n
    \r\n
  • Diagnosis of probable AD as defined by National Institute of Neurological and Communicative Disorders and Stroke (NINCDS) and the Alzheimer's Disease and Related Disorders Association (ADRDA) guidelines.

  • \r\n
  • Mild to moderate severity of AD will be defined by the Mini-Mental State Exam as follows:

  • \r\n
  • Mini-Mental State Examination (MMSE) score of 10 to 23.

  • \r\n
  • The absence of other causes of dementia will be performed by clinical opinion and by the following:

  • \r\n
  • Hachinski Ischemic Scale score of ≤4.

  • \r\n
  • CNS imaging (CT scan or MRI of brain) compatible with AD within past 1 year (see Section 3.4.2.1).

  • \r\n
", + "

Approximately 100 patients will be randomized to each of the 3 treatment groups. Previous experience with the oral formulation of xanomeline suggests that this sample size has 90% power to detect a 3.0 mean treatment difference in ADAS-Cog (p<.05, two-sided), based on a standard deviation of 6.5. Furthermore, this sample size has 80% power to detect a 0.36 mean treatment difference in CIBIC+ (p<.05, two-sided), based on a standard deviation of 0.9.

", + "

Commencing at Visit 1, all patients will be assigned an identification number. This identification number and the patient's three initials must appear on all patient-related documents submitted to Lilly.

\r\n

When qualified for enrollment at Visit 3 the patient will be randomized to 1 of 3 treatment arms.

", + "
", + "
\r\n\r\n\r\n\r\n\r\n\r\n\r\n

Primary Study Material:

Xanomeline

TTS (adhesive patches)

50 cm 2 , 54 mg* 25 cm 2 , 27 mg*

Comparator Material:

Placebo

TTS

Identical in appearance to primary study material

\r\n

*All doses are measured in terms of the xanomeline base.

\r\n

Patches should be stored at controlled room temperature, and all used patches must be handled and disposed of as biohazardous waste.

\r\n

For a detailed description of the composition of these formulations please refer to Part II, Section 14 of the Xanomeline (LY246708) Clinical Investigator's Brochure.

", + "

To test acute tolerance of transdermal formulation, patients will have a TTS (placebo) administered at the start of Visit 1, and removed at the conclusion of Visit 1. The patient's and caregiver's willingness to comply with 26 weeks of transdermal therapy should be elicited, and those patients/caregivers unwilling to comply should be excluded.

\r\n

Upon enrollment at Visit 3, and on the morning of each subsequent day of therapy , xanomeline or placebo will be administered with the application of 2 adhesive patches, one 50 cm2 in area, the other 25 cm2 in area. Each morning, prior to the application of the patches, hydrocortisone cream (1%) should be applied to the skin at the intended site of administration, rubbed in, and allowed to penetrate for approximately 30 minutes. Thereafter, excess cream should be wiped away and the patches applied.

\r\n

The patches are to be worn continuously throughout the day, for a period of approximately 12 to 14 hours, and removed in the evening. After removal of the patches, hydrocortisone cream (1%) should be applied locally to the site of administration.

\r\n

Patches should be applied to a dry, intact, non-hairy area. Applying the patch to a shaved area is not recommended. The application site of the patches should be rotated according to the following schedule:

\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n

Day

Patch Location

Sunday

right or left upper arm

Monday

right or left upper back

Tuesday

right or left lower back (above belt line)

Wednesday

right or left buttocks

Thursday

right or left mid-axillary region

Friday

right or left upper thigh

Saturday

right or left upper chest

\r\n

Patients and caregivers are free to select either the left or right site within the constraints of the rotation schedule noted above. Patches should be applied at approximately the same time each day. For patients who habitually bathe in the morning, the patient should bathe prior to application of new patches. Every effort should be taken to allow for morning administration of the patches. Exceptions allowing administration of TTS patches at night instead of in the morning will be made on a case-by-case basis by the CRO medical monitor. In the event that some adhesive remains on the patient's skin and cannot be removed with normal bathing, a special solution will be provided to remove the adhesive.

\r\n

Following randomization at Visit 3, patients will be instructed to call the site if they have difficulty with application or wearing of patches. In the event that a patch becomes detached, a new patch of the same size should be applied (at earliest convenience) to an area of the dermis adjacent to the detachment site, and the rotation schedule should be resumed the following morning. If needed, the edges of the patch may be secured with a special adhesive tape that will be provided. If daily doses are reduced, improperly administered, or if a patch becomes detached and requires application of a new patch on three or more days in any 30-day period, the CRO research physician will be notified.

\r\n

If the daily dose is reduced or improperly administered in the 24 hours prior to any scheduled clinic visit, the visit should be rescheduled (except for early termination and retrieval visits).

\r\n

Patients must be instructed to return all used and unused study drug to the investigator at each visit for proper disposal and CT reconciliation by the investigator.

", + "

The study will be double-blind. To further preserve the blinding of the study, only a minimum number of Lilly and CRO personnel will see the randomization table and codes before the study is complete.

\r\n

Emergency codes generated by a computer drug-labeling system will be available to the investigator. These codes, which reveal the patients treatment group, may be opened during the study only if the choice of follow-up treatment depends on the patient's therapy assignment.

\r\n

The investigator should make every effort to contact the clinical research physician prior to unblinding a patient's therapy assignment. If a patient's therapy assignment is unblinded, Lilly must be notified immediately by telephone. After the study, the investigator must return all sealed and any opened codes.

", + "

Intermittent use of chloral hydrate, zolpidem, or lorazepam is permitted during this clinical trial as indicated for agitation or sleep. If medication is required for agitation for a period exceeding 1 week, a review of the patient's status should be made in consultation with the CRO research physician. Caregivers and patients should be reminded that these medications should not be taken within 24 hours of a clinic visit (including the enrollment visit), and administration of efficacy measures should be deferred if the patient has been treated with these medications within the previous 24 hours.

\r\n

If an antihistamine is required during the study, Claritin® (loratadine) or Allegra® (fexofenadine hydrochloride) are the preferred agents, but should not be taken within 24 hours of a clinic visit. Intermittent use (per package insert) of antitussives (containing antihistamines or codeine) and select narcotic analgesics (acetaminophen with oxycodone, acetaminophen with codeine) are permitted during the trial. Caregivers and patients should be reminded that antihistamines and narcotics should not be taken within 3 days of a clinic efficacy visit (including enrollment visit). If an H 2 blocker is required during the study, Axid® (nizatidine) will be permitted on a case-by-case basis by the CRO medical monitor. For prostatic hypertrophy, small doses (2 mg per day) of Hytrin® (terazosin) or Cardura® (doxazosin) will be permitted on a case-by-case basis. Please consult the medical monitor. The calcium channel blockers Cardene® (nicardipine),

\r\n

Norvasc® (amlodipine), and DynaCirc® (isradipine) are allowed during the study. If a patient has been treated with any medication within disallowed time periods prior to the clinic visit, efficacy measures should be deferred.

\r\n

Other classes of medications not stated in Exclusion Criteria, Section 3.4.2.2, will be permitted. Patients who require treatment with an excluded medication (Section 3.4.2.2) will be discontinued from the study following consultation with the CRO research physician.

", + "
", + "

See Schedule of Events, Attachment LZZT.1 for the times of the study at which efficacy data will be collected.

", + "

The following measures will be performed in the course of the study. At Visits 3, 8, 10, and 12, ADAS-Cog, CIBIC+, and DAD will be administered. NPI-X will be administered at 2-week intervals either at clinic visits or via a telephone interview. Efficacy measures will also be collected at early termination visits, and at the retrieval visit. The neuropsychological assessment should be performed first; other protocol requirements, such as labs and the physical, should follow.

\r\n
    \r\n
  1. Alzheimer's Disease Assessment Scale - Cognitive Subscale (ADAS-Cog): ADAS-Cog is an established measure of cognitive function in Alzheimer's Disease. This scale has been incorporated into this study by permission of Dr. Richard C. Mohs and the American Journal of Psychiatry and was adapted from an article entitled, “The Alzheimer's Disease Assessment Scale (ADAS),” which was published in the American Journal of Psychiatry, Volume No.141, pages 1356-1364, November, 1984, Copyright 1984.

    \r\n

    The ADAS-Cog (11) and the ADAS-Cog (14): The ADAS-Cog (11) is a standard 11-item instrument used to assess word recall, naming objects, commands, constructional praxis, ideational praxis, orientation, word recognition tasks, spoken language ability, comprehension, word finding difficulty, and recall of test instructions. For the purposes of this study, three items (delayed word recall, attention/visual search task, and maze solution) have been added to the ADAS-Cog (11) to assess the patient's attention and concentration. The 14 item instrument will be referred to as the ADAS-Cog (14). At each efficacy visit, all 14 items will be assessed, and in subsequent data analyses, performance on the ADAS-Cog (14) and performance on the subset ADAS-Cog (11) will be considered.

  2. \r\n
  3. Video-referenced Clinician's Interview-Based Impression of Change (CIBIC+): The CIBIC+ is an assessment of the global clinical status relative to baseline. The CIBIC+ used in this study is derived from the Clinical Global Impression of Change, an instrument in the public domain, developed by the National Institute on Aging Alzheimer's Disease Study Units Program (1 U01 AG10483; Leon Thal, Principal Investigator). The instrument employs semi-structured interviews with the patient and caregiver, to assess mental/cognitive state, behavior, and function. These domains are not individually scored, but rather are aggregated in the assignment of a global numeric score on a 1 to 7 scale (1 = marked improvement; 4 = no change; and 7 = marked worsening).

    \r\n

    The clinician assessing CIBIC+ will have at least one year of experience with the instrument and will remain blinded to all other efficacy and safety measures.

  4. \r\n
  5. Revised Neuropsychiatric Inventory (NPI-X): The NPI-X is an assessment of change in psychopathology in patients with dementia. The NPI-X is administered to the designated caregiver. This instrument has been revised from its original version (Cummings et al. 1994) and incorporated into this study with the permission of Dr. Jeffrey L. Cummings.

  6. \r\n
  7. Disability Assessment for Dementia (DAD): The DAD is used to assess functional abilities of activities of daily living (ADL) in individuals with cognitive impairment. This scale has been revised and incorporated into this study by permission of Louise Gauthier, M.Sc., and Dr. Isabelle Gelinas. The DAD is administered to the designated caregiver.

  8. \r\n
\r\n

For each instrument, each assessment is to be performed by the same trained health care professional. If circumstances preclude meeting this requirement, the situation is to be documented on the Clinical Report Form (CRF), and the CRO research physician is to be notified.

\r\n

In addition to the efficacy measures noted above, a survey form will be used to collect information from the caregiver on TTS acceptability (Attachment LZZT.9).

", + "

Group mean changes from baseline in the primary efficacy parameters will serve as efficacy criteria. The ADAS-Cog (11) and the video-referenced CIBIC+ will serve as the primary efficacy instruments. Secondary efficacy instruments will include the DAD, the NPI-X, and the ADAS-Cog (14). The procedures and types of analyses to be done are outlined in Section 4.

\r\n

The primary analysis of efficacy will include only the data obtained up to and including the visit of discontinuation of study drug. Furthermore, the primary analysis will not include efficacy data obtained at any visit where the study drug was not administered in the preceding three days. Analyses that include the retrieved dropouts are considered secondary.

", + "

Blood samples (7 mL) for the determination of xanomeline concentrations in plasma will be collected from each patient at Visits 3, 4, 5, 7, 9, and 11. The blood sample drawn at Visit 3 is a baseline sample. The remaining 5 clinic visits should be scheduled so that 1 blood sample is collected at any time during each of the following intervals: early AM visit (hold application of new patch until after blood sample is collected); 9AM to 11AM; 11AM to 1PM; 1PM to 3PM; and 3PM to 5PM. Collection of blood samples during each of these intervals should not occur in any particular order, nor should they occur in the same order for each patient. Every effort should be made to comply with the suggested sampling times. This blood-sampling schedule is based on a sparse sampling strategy where only a few samples will be collected from each patient. The most crucial aspect of the sampling design is to record the date and exact time the sample was drawn and to record the date and time of patch application on the day of the clinic visit and the previous 2 days.

\r\n

If a patient is discontinued from the study prior to protocol completion, a pharmacokinetic blood sample should be drawn at the early discontinuation visit. The date and exact time the sample was drawn and the date of the last patch application should be recorded.

\r\n

Immediately after collection, each sample will be centrifuged at approximately 177 × G for 15 minutes. The plasma will be transferred into a polypropylene tube bearing the identical label as the blood collection tube. Samples will be capped and frozen at approximately −20°C. Care must be taken to insure that the samples remain frozen during transit.

\r\n

The samples will be shipped on dry ice to Central Laboratory.

", + "

Investigators are responsible for monitoring the safety of patients who have entered this study and for alerting CRO to any event that seems unusual, even if this event may be considered an unanticipated benefit to the patient. See Section 3.9.3.2.1.

\r\n

Investigators must ensure that appropriate medical care is maintained throughout the study and after the trial (for example, to follow adverse events).

", + "

Safety measures will be performed at designated times by recording adverse events, laboratory test results, vital signs (including supine/standing pulse and blood pressure readings) ECG monitoring, and Ambulatory ECGs (see Schedule of Events, Attachment LZZT.1).

", + "

Lilly has standards for reporting adverse events that are to be followed, regardless of applicable regulatory requirements that are less stringent. For purposes of collecting and evaluating all information about Lilly drugs used in clinical trials, an adverse event is defined as any undesirable experience or an unanticipated benefit (see Section 3.9.3.2.1) that occurs after informed consent for the study has been obtained, without regard to treatment group assignment, even if no study medication has been taken. Lack of drug effect is not an adverse event in clinical trials, because the purpose of the clinical trial is to establish drug effect.

\r\n

At the first visit, study site personnel will question the patient and will note the occurrence and nature of presenting condition(s) and of any preexisting condition(s). At subsequent visits, site personnel will again question the patient and will note any change in the presenting condition(s), any change in the preexisting condition(s), and/or the occurrence and nature of any adverse events.

", + "

All adverse events must be reported to CRO via case report form.

\r\n

Study site personnel must report to CRO immediately, by telephone, any serious adverse event (see Section 3.9.3.2.2 below), or if the investigator unblinds a patient's treatment group assignment because of an adverse event or for any other reason.

\r\n

If a patient's dosage is reduced or if a patient is discontinued from the study because of any significant laboratory abnormality, inadequate response to treatment, or any other reason, the circumstances and data leading to any such dosage reduction or discontinuation must be reported and clearly documented by study site personnel on the clinical report form.

\r\n

An event that may be considered an unanticipated benefit to the patient (for example, sleeping longer) should be reported to CRO as an adverse event on the clinical report form. “Unanticipated benefit” is a COSTART classification term. In cases where the investigator notices an unanticipated benefit to the patient, study site personnel should enter the actual term such as “sleeping longer,” and code “unanticipated benefit” in the clinical report form adverse event section.

\r\n

Solicited adverse events from the skin rash questionnaire (see Section 3.9.3.4) should be reported on the questionnaire only and not also on the adverse event clinical report form

", + "

Study site personnel must report to CRO immediately, by telephone, any adverse event from this study that is alarming or that:

\r\n
    \r\n
  • Results in death

  • \r\n
  • Results in initial or prolonged inpatient hospitalization

  • \r\n
  • Is life-threatening

  • \r\n
  • Results in severe or permanent disability

  • \r\n
  • Results in cancer [(other than cancers diagnosed prior to enrollment in studies involving patients with cancer)]

  • \r\n
  • Results in a congenital anomaly

  • \r\n
  • Is a drug overdose

  • \r\n
  • Is significant for any other reason.

  • \r\n
\r\n

Definition of overdose: For a drug under clinical investigation, an overdose is any intentional or unintentional consumption of the drug (by any route) that exceeds the dose recommended in the Clinical Investigator's Brochure or in an investigational protocol, whichever dose is larger. For a marketed drug, a drug overdose is any intentional or unintentional consumption of the drug (by any route) that exceeds the dose listed in product labeling, even if the larger dose is prescribed by a physician.

", + "

Table LZZT.1 lists the clinical laboratory tests that will be performed at Visit 1.

\r\n

Table LZZT.1. Laboratory Tests Performed at Admission (Visit 1)

\r\n

Safety Laboratory Tests

\r\n\r\n\r\n\r\n\r\n\r\n
\r\n

Hematology:

\r\n
    \r\n
  • Hemoglobin
  • \r\n
  • Hematocrit
  • \r\n
  • Erythrocyte count (RBC)
  • \r\n
  • Mean cell volume (MCV)
  • \r\n
  • Mean cell hemoglobin (MCH)
  • \r\n
  • Mean cell hemoglobin concentration (MCHC)
  • \r\n
  • Leukocytes (WBC)
  • \r\n
  • Neutrophils, segmented
  • \r\n
  • Neutrophils, juvenile (bands)
  • \r\n
  • Lymphocytes
  • \r\n
  • Monocytes
  • \r\n
  • Eosinophils
  • \r\n
  • Basophils
  • \r\n
  • Platelet
  • \r\n
  • Cell morphology
  • \r\n
\r\n

Urinalysis:

\r\n
    \r\n
  • Color
  • \r\n
  • Specific gravity
  • \r\n
  • pH
  • \r\n
  • Protein
  • \r\n
  • Glucose
  • \r\n
  • Ketones
  • \r\n
  • Bilirubin
  • \r\n
  • Urobilinogen
  • \r\n
  • Blood
  • \r\n
  • Nitrite
  • \r\n
  • Microscopic examination of sediment
  • \r\n
\r\n
\r\n

Clinical Chemistry - Serum Concentration of:

\r\n
    \r\n
  • Sodium
  • \r\n
  • Potassium
  • \r\n
  • Bicarbonate
  • \r\n
  • Total bilirubin
  • \r\n
  • Alkaline phosphatase (ALP)
  • \r\n
  • Gamma-glutamyl transferase (GGT)
  • \r\n
  • Alanine transaminase (ALT/SGPT)
  • \r\n
  • Aspartate transaminase (AST/SGOT)
  • \r\n
  • Blood urea nitrogen (BUN)
  • \r\n
  • Serum creatinine
  • \r\n
  • Uric acid
  • \r\n
  • Phosphorus
  • \r\n
  • Calcium
  • \r\n
  • Glucose, nonfasting
  • \r\n
  • Total protein
  • \r\n
  • Albumin
  • \r\n
  • Cholesterol
  • \r\n
  • Creatine kinase (CK)
  • \r\n
\r\n

Thyroid Function Test (Visit 1 only):

\r\n
    \r\n
  • Free thyroid index
  • \r\n
  • T3 Uptake
  • \r\n
  • T4
  • \r\n
  • Thyroid-stimulating hormone (TSH)
  • \r\n
\r\n

Other Tests (Visit 1 only):

\r\n
    \r\n
  • Folate
  • \r\n
  • Vitamin B 12
  • \r\n
  • Syphilis screening
  • \r\n
  • Hemoglobin A1C (IDDM patients only)
\r\n
\r\n

Laboratory values that fall outside a clinically accepted reference range or values that differ significantly from previous values must be evaluated and commented on by the investigator by marking CS (for clinically significant) or NCS (for not clinically significant) next to the values. Any clinically significant laboratory values that are outside a clinically acceptable range or differ importantly from a previous value should be further commented on in the clinical report form comments page.

\r\n

Hematology, and clinical chemistry will also be performed at Visits 4, 5, 7, 8, 9, 10, 11, 12, and 13. Patients that experience a rash and/or eosinophilia may have additional hematology samples obtained as described in 3.9.3.4 (Other Safety Measures).

\r\n

Urinalysis will also be performed at Visits 4, 9, and 12. The following criteria have been developed to monitor hepatic function.

\r\n
    \r\n
  • Patients with ALT/SGPT levels >120 IU will be retested weekly.

  • \r\n
  • Patients with ALT/SGPT values >400 IU, or alternatively, an elevated ALT/SGPT accompanied by GGT and/or ALP values >500 IU will be retested within 2 days. The sponsor's clinical research administrator or clinical research physician is to be notified. If the retest value does not decrease by at least 10%, the study drug will be discontinued; additional laboratory tests will be performed until levels return to normal. If the retest value does decrease by 10% or more, the study drug may be continued with monitoring at 3 day intervals until ALT/SGPT values decrease to <400 IU or GGT and/or ALP values decrease to <500 IU. \r\n

", + "
Patients experiencing Rash and/or Eosinophilia\r\n

The administration of placebo and xanomeline TTS is associated with a rash and/or eosinophilia in some patients. The rash is characterized in the following ways:

\r\n
    \r\n
  • The rash is confined to sites of application.

  • \r\n
  • The rash may be associated with pruritus.

  • \r\n
  • In 5% of cases of rash observed in the Interim Analysis, blistering has been observed.

  • \r\n
  • The onset of rash may occur at any time during the course of the study.

  • \r\n
  • A moderate eosinophilia (0.6-1.5 x 103 /microliter) is associated with rash and has been noted in approximately 10% of patients.

  • \r\n
\r\n

It does not appear that the rash constitutes a significant safety risk; however, it could affect the well-being of the patients. The following monitoring is specified:

\r\n

Skin Rash Follow-up

\r\n

For patients who exit the study or its extension with rash at the site(s) of application:

\r\n
    \r\n
  1. Approximately 2 weeks after the last visit, the study site personnel should contact the patient/caregiver by phone and complete the skin rash questionnaire. (Note: those patients with rash who have previously exited the study or its extension should be contacted at earliest convenience.)

  2. \r\n
  3. If caregiver states unequivocally that skin problems have completely resolved, no further follow-up is needed.

  4. \r\n
  5. If caregiver reports scarring and/or other problems, patient should return to clinic for a follow-up visit. The skin rash questionnaire should again be completed. If in the opinion of the investigator, further follow-up is required, contact the CRO medical monitor. Completed skin rash questionnaires should be faxed to CRO.

  6. \r\n
\r\n

Completion of the questionnaires will create a separate data set for solicited adverse events. In completing these forms please note the following:

\r\n
    \r\n
  1. Solicited events (events discovered as result of completion of follow-up questionnaires) should be reported on questionnaire page only.

  2. \r\n
  3. Spontaneously reported adverse events (events presented by the patient without direct questioning of the event) should be reported as described in 3.9.3.2 .1 (Adverse Event Reporting Requirements).

  4. \r\n
\r\n

Serious adverse events should be handled and reported as described in 3.9.3.2.1 without regard to whether the event is solicited or spontaneously reported.

\r\n

Eosinophilia Follow-up

\r\n
    \r\n
  1. For patients that are currently in the study with eosinophil counts greater than 0. 6x10 3 /microliter:

    \r\n
    • Repeat hematology at each visit until resolved in the opinion of the investigator.

  2. \r\n
  3. For patients that are currently in the study with eosinophil counts greater than 1.5x10 3 /microliter:

    \r\n
    • Obtain hematology profile every 2 weeks until resolved or explained by other causes in the opinion of the investigator.

    • \r\n
    • Notify CRO medical monitor.

    • \r\n
  4. \r\n
  5. For patients with eosinophil counts greater than 0.6x10 3 /microliter at exit \r\nfrom the study or its extension:

    \r\n
      \r\n
    • Obtain hematology profile approximately every 2 weeks until resolved or, in the opinion of the investigator, explained by other causes. (Note: patients with eosinophil counts greater than 0.6x10 3 /microliter who have previously exited the study or its extension should return for hematology profile at earliest convenience.)

    • \r\n
  6. \r\n
", + "

Patient should lie supine quietly for at least 5 minutes prior to vital signs measurement. Blood pressure should be measured in the dominant arm with a standardized mercury manometer according to the American Heart Association standard recommendations. Diastolic blood pressure will be measured as the point of disappearance of the Korotkoff sounds (phase V). Heart rate will be measured by auscultation. Patient should then stand up. Blood pressure should again be measured in the dominant arm and heart rate should be measured after approximately 1 and 3 minutes.

\r\n

An automated blood pressure cuff may be used in place of a mercury manometer if it is regularly (at least monthly) standardized against a mercury manometer.

", + "

Cardiovascular status will be assessed during the trial with the following measures:

\r\n
    \r\n
  • All patients will be screened by obtaining a 12-lead ECG, and will have repeat ECGs performed at Visits 4, 5, 7, 8, 9, 10, 11, 12, 13, and early termination (ET) (see Schedule of Events, Attachment LZZT.1).

  • \r\n
  • All patients will undergo a 24-hour Ambulatory ECG at Visit 2 (prior to the initiation of study medication). Although every effort will be made to obtain the entire 24-hour ambulatory ECG recording, this may not always be feasible because of patient behavior or technical difficulties. The minimal recording period for an ambulatory ECG to be considered interpretable will be 8 hours, of which at least 3 hours must be sleep.

  • \r\n
  • The incidence of syncope, defined as an observed loss of consciousness and muscle tone not attributable to transient ischemic attack or to seizure, will be closely monitored. Caregivers will be instructed to report any instance of syncopal episodes to the investigator within 24 hours. The investigator should immediately report such events to the CRO research physician. The CRO research physician will make a clinical assessment of each episode, and with the investigator determine if continuation of \r\ntherapy is appropriate. These findings will be reported to the Lilly research physician immediately.

  • \r\n
", + "

The CRO research physician will monitor safety data throughout the course of the study.

\r\n

Cardiovascular measures, including ECGs and 24-hour Ambulatory ECGs (see Section 3.9.3.4.2) will be monitored on an ongoing basis as follows:

\r\n
    \r\n
  • As noted in Section 3.9.3.4.2, all patients will be screened by obtaining a 12-lead ECG, and will have repeat ECGs performed at Visits 4, 5, 7, 8, 9, 10, 11, 12, 13, and early termination (ET) (see Schedule of Events for Protocol H2Q-MC-LZZT(c), Attachment LZZT.1). ECG data will be interpreted at the site and express mailed overnight to a central facility which will produce a report within 48 hours. The report will be forwarded to the investigator. At screening, the report of the central facility will be used to exclude patients according to criteria specified in Section 3.4.2.2. If, during the treatment phase of the study, review of ECG data (either at the site or at the central facility) reveals left bundle branch block, bradycardia ≤50 beats per minute, sinus pauses >2 seconds, second degree heart block, third degree heart block, Wolff-Parkinson-White syndrome, sustained supraventricular tachyarrhythmia, or ventricular tachycardia at a rate of ≥120 beats per minute lasting ≥10 seconds, the investigator, the Lilly research physician, the CRO research physician, and the cardiologist chairing the DSMB will be notified immediately, and discontinuation of the patient will be considered.

  • \r\n
  • As noted in Section 3.9.3.4.2, all patients will undergo a 24-hour Ambulatory ECG at Visit 2 (prior to the initiation of study medication). Ambulatory ECG data from Visit 2 will be express mailed overnight to a central facility which will produce a report within 24 hours. The report will be forwarded to the investigator. If a report documents sustained ventricular tachycardia with rate >120 beats per minute, third degree heart block, or sinus pauses of >6.0 seconds, the investigator, the Lilly research \r\nphysician, the CRO research physician, and the cardiologist chairing the DSMB will be notified immediately, and the patient will be discontinued. If any report documents sinus pauses of >3.0 seconds or second degree heart block, the CRO research physician, and Lilly research physician, and cardiologist chairing the DSMB will be immediately notified and the record will be reviewed within 24 hours of notification by the cardiologist chairing the DSMB.

  • \r\n
\r\n

In addition to ongoing monitoring of cardiac measures, a comprehensive, periodic review of cardiovascular safety data will be conducted by the DSMB, which will be chaired by an external cardiologist with expertise in arrhythmias, their pharmacological bases, and their clinical implications. The membership of the board will also include two other external cardiologists, a cardiologist from Lilly, a statistician from Lilly, and the Lilly research physician. Only the three external cardiologists will be voting members.

\r\n

After approximately 75 patients have completed 1 month of treatment, the DSMB will meet to decide:

\r\n
    \r\n
  • If discontinuation of the study or any treatment arm is appropriate

  • \r\n
  • If additional cardiovascular monitoring is required

  • \r\n
  • If further cardiovascular monitoring is unnecessary

  • \r\n
  • If adjustment of dose within a treatment arm (or arms) is appropriate.

  • \r\n
\r\n

If necessary, this analysis will be repeated after 150 patients have completed 1 month of treatment, after 225 patients have completed 1 month of treatment, and after 300 patients have completed 1 month of treatment. Primary consideration will be given to the frequency of pauses documented in Ambulatory ECG reports. The number of pauses greater than or equal to 2, 3, 4, 5, and 6 seconds will be tabulated. Primary analysis will focus on the number of pauses greater than or equal to 3 seconds.

\r\n

In the event of a high incidence of patient discontinuation due to syncope, the following guideline may be employed by the DSMB in determining if discontinuation of any treatment arm is appropriate. If the frequency of syncope in a xanomeline treatment arm relative to the frequency of syncope in the placebo arm equals or exceeds the following numbers, then consideration will be given to discontinuing that treatment arm. The Type I error rate for this rule is approximately 0.032 if the incidence in each group is 0.04. The power of this rule is 0.708 if the incidence is 0.04 for placebo and 0.16 for xanomeline TTS.

\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n

Placebo

Xanomeline

PlaceboXanomeline

0

6

615

1

7

716

2

9

817

3

11

918

4

12

1020

5

13

X2X (2-fold)
\r\n

This rule has been used in other studies for monitoring spontaneous events with an incidence of less than 10%. This rule is constructed assuming a 2-group comparison with each group having a final sample size of 100. Unblinding which occurs during these analyses will be at the group level and will be documented.

\r\n

The stopping rule based on Ambulatory ECG findings is as follows:

\r\n

If the number of patients experiencing a pause of ≥6 seconds in a xanomeline treatment arm relative to the number of patients in the placebo arm equals or exceeds the numbers in the following table, then that treatment arm will be discontinued. The Type I error rate for this rule is approximately 0.044 if the incidence in each group is 0.01. The power of this rule is 0.500 if the incidence is 0.01 for placebo and 0.04 for xanomeline TTS.

\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n

Placebo

Xanomeline

0

3

1

5

2

6

3

7

4

8

x

2x

", + "

The medications and efficacy measurements have been used in other studies in elderly subjects and patients.

", + "
", + "

Participation in the study shall be terminated for any patient who is unable or unwilling to comply with the study protocol or who develops a serious adverse event.

\r\n

In addition, patients may be discontinued for any of the following reasons:

\r\n
    \r\n
  • In the opinion of the investigator, a significant adverse event occurs or the \r\nsafety of the patient is otherwise compromised.

  • \r\n
  • The patient requests to be withdrawn from the study.

  • \r\n
  • The physician in charge of the study or Lilly, for any reason stops the \r\npatient's participation in the study.

  • \r\n
\r\n

If a patient's participation terminates early, an early termination visit should be scheduled. Upon decision to discontinue a patient from the study, the patient's dose should be titrated down by instructing the patient to immediately remove the 25-cm2 patch. Patients should be instructed to continue to apply a 50-cm2 patch daily until the early termination visit, at which time the drug will be discontinued. Physical exam, vital signs, temperature, use of concomitant medications, chemistry/hematology/urinalysis labs, xanomeline plasma sample, TTS acceptability survey, efficacy measures, adverse events, and an ECG will be collected at the early termination visit.

\r\n

In the event that a patient's participation or the study itself is terminated, the patient shall return all study drug(s) to the investigator.

", + "

If possible, patients who have terminated early will be retrieved on the date which would have represented Visit 12 (Week 24). Vital signs, temperature, use of concomitant medications, adverse events, and efficacy measure assessment will be gathered at this visit. If the patient is not retrievable, this will be documented in the source record.

", + "

All patients who are enrolled in the study will be included in the efficacy analysis and the safety analysis. Patients will not be excluded from the efficacy analysis for reasons such as non-compliance or ineligibility, except for the time period immediately preceding the efficacy assessment (see Section 3.9.1.2).

", + "

Patients who successfully complete the study will be eligible for participation in an openlabel extension phase, where every patient will be treated with active agent. The patients who elect to participate in the open-label extension phase will be titrated to their maximally titrated dose. This open-label extension phase will continue until the time the product becomes marketed and is available to the public or until the project is discontinued by the sponsor. Patients may terminate at any time at their request.

", + "

Because patients enrolled in this study will be outpatients, the knowledge that patients have taken the medication as prescribed will be assured in the following ways:

\r\n
    \r\n
  1. Investigators will attempt to select those patients and caregivers who \r\nhave been judged to be compliant.

  2. \r\n
  3. Study medication including unused, partially used, and empty patch \r\ncontainers will be returned at each clinical visit so that the remaining \r\nmedication can be counted by authorized investigator staff (nurse, \r\npharmacist, or physician). The number of patches remaining will be \r\nrecorded on the CRF.

  4. \r\n
  5. Following randomization at Visit 3, patients will be instructed to call \r\nthe site if they have difficulty with application or wearing of patches. If \r\ndaily doses are reduced, improperly administered, or if a patch becomes \r\ndetached and requires application of a new patch on three or more days \r\nin any 30-day period, the CRO research physician will be notified.

  6. \r\n
\r\n

If the daily dose is reduced or improperly administered in the 24 hours prior to any scheduled clinic visit, the visit should be rescheduled (except for early termination and retrieval visits).

", + "

To ensure both the safety of participants in the study, and the collection of accurate, complete, and reliable data, Lilly or its representatives will perform the following activities:

\r\n
    \r\n
  • Provide instructional material to the study sites, as appropriate.

  • \r\n
  • Sponsor a start-up training session to instruct the investigators and study \r\ncoordinators. This session will give instruction on the protocol, the \r\ncompletion of the clinical report forms, and study procedures.

  • \r\n
  • Make periodic visits to the study site.

  • \r\n
  • Be available for consultation and stay in contact with the study site \r\npersonnel by mail, telephone, and/or fax.

  • \r\n
  • Review and evaluate clinical report form data and use standard computer \r\nedits to detect errors in data collection.

  • \r\n
\r\n

To ensure the safety of participants in the study and to ensure accurate, complete, and reliable data, the investigator will do the following:

\r\n
    \r\n
  • Keep records of laboratory tests, clinical notes, and patient medical records in the patient files as original source documents for the study.

  • \r\n
\r\n

Lilly or its representatives may periodically check a sample of the patient data recorded against source documents at the study site. The study may be audited by Lilly Medical Quality Assurance (MQA) and/or regulatory agencies at any time. Investigators will be given notice before an MQA audit occurs.

", + "
", + "

In general, all patients will be included in all analyses of efficacy if they have a baseline measurement and at least one postrandomization measurement. Refer to Section 3.9.1.2. for a discussion of which specific efficacy data will be included in the primary analysis.

\r\n

In the event that the doses of xanomeline TTS are changed after the study starts, the analysis will be of three treatment groups (high dose, low dose, and placebo), even though patients within the high dose treatment group, for example, may not all be at exactly the same dose. Also, if the dose is changed midway through the study, the mean dose within each group will be used in the dose response analysis described in Section 4.3.3.

\r\n

All analyses described below will be conducted using the most current production version of SAS® available at the time of analysis.

", + "

All measures (for example, age, gender, origin) obtained at either Visits 1, 2, or 3, prior to randomization, will be summarized by treatment group and across all treatment groups. The groups will be compared by analysis of variance (ANOVA) for continuous variables and by Pearson's chi-square test for categorical variables. Note that because patients are randomized to 1 of the 3 treatment groups, any statistically significant treatment group differences are by definition a Type I error; however, the resulting p-values will be used as another descriptive statistic to help focus possible additional analyses (for example, analysis of covariance, subset analyses) on those factors that are most imbalanced (that is, that have the smallest p-values).

", + "
", + "

Efficacy measures are described in Section 3.9.1.1. As stated in Section 3.9.1.2, the primary outcome measures are the ADAS-Cog (11) and CIBIC+ instruments. Because both of these variables must reach statistical significance, an adjustment to the nominal p-values is necessary in order to maintain a .05 Type I error rate for this study. This adjustment is described in detail in Section 4.3.5.

\r\n

The DAD will be analyzed with respect to the total score, as well as the subscores of \r\ninitiation, planning and organization, and effective performance. This variable is \r\nconsidered a secondary variable in the US, but is a third primary variable in Europe.

\r\n

The NPI-X is a secondary variable. The primary assessment of this instrument will be for the total score, not including the sleep, appetite, and euphoria domains. This total score is computed by taking the product of the frequency and severity scores and summing them up across the domains. Secondary variables derived from the NPI-X include evaluating each domain/behavior separately. Also, caregiver distress from the NPI-X will be analyzed.

\r\n

ADAS-Cog (14) and each of the 14 individual components will also be analyzed. In addition, a subscore of the ADAS-Cog will be computed and analyzed, based on results from a previous large study of oral xanomeline. This subscore, referred to as ADAS-Cog (4), will be the sum of constructional praxis, orientation, spoken language ability, and word finding difficulty in spontaneous speech.

\r\n

Any computed total score will be treated as missing if more than 30% of the items are missing or scored “not applicable”. For example, when computing ADAS-Cog(11), if 4 or more items are missing, then the total score will not be computed. When one or more items are missing (but not more than 30%), the total score will be adjusted in order to maintain the full range of the scale. For example, ADAS-Cog(11) is a 0-70 scale. If the first item, Word Recall (ranges from 0 to 10), is missing, then the remaining 10 items of the ADAS-Cog(11) will be summed and multiplied by (70 / (70-10) ), or 7/6. This computation will occur for all totals and subtotals of ADAS-Cog and NPI-X. DAD is a 40 item questionnaire where each question is scored as either “0” or “1”. The DAD total score and component scores are reported as percentage of items that are scored “1”. So if items of the DAD are “not applicable” or missing, the percentage will be computed for only those items that are scored. As an example, if two items are missing (leaving 38 that are scored), and there are 12 items scored as “1”, the rest as “0”, then the DAD score is 12/38=.316.

", + "

Baseline data will be collected at Visit 3.

\r\n

The primary analysis of ADAS-Cog (11) and CIBIC+ will be the 24-week endpoint, which is defined for each patient and variable as the last measurement obtained postrandomization (prior to protocol defined reduction in dose).

\r\n

Similar analyses at 24 weeks will be conducted for the secondary efficacy variables. Analysis of patients who complete the 24-week study will also be conducted for all efficacy variables; this is referred to as a “completer” analysis.

\r\n

Additionally, each of the efficacy variables will be analyzed at each time point both as “actual cases,” that is, analyzing the data collected at the various time points, and also as a last-observation-carried-forward (LOCF). Note that the LOCF analysis at 24 weeks is the same as the endpoint analysis described previously.

\r\n

Several additional analyses of NPI-X will be conducted. Data from this instrument will be collected every 2 weeks, and represent not the condition of the patient at that moment in time, but rather the worst condition of the patient in the time period since the most recent NPI-X administration. For this reason, the primary analysis of the NPI-X will be of the average of all postrandomization NPI-X subscores except for the one obtained at Week 2. In the event of early discontinuations, those scores that correspond to the interval between Weeks 2 to 24 will be averaged. The reason for excluding Week 2 data from this analysis is that patients could be confused about when a behavior actually stops after randomization; the data obtained at Week 2 could be somewhat “tainted.” Also, by requiring 2 weeks of therapy prior to use of the NPI-X data, the treatment difference should be maximized by giving the drug 2 weeks to work, thereby increasing the statistical power. Secondary analyses of the NPI-X will include the average of all postrandomization weeks, including measures obtained at Weeks 2 and 26.

", + "

The primary method to be used for the primary efficacy variables described in Sections 4.3.1 and 4.3.2 will be analysis of covariance (ANCOVA), except for CIBIC+ which is a score that reflects change from baseline, so there is no corresponding baseline CIBIC+ score. Effects in the ANCOVA model will be the corresponding baseline score, investigator, and treatment. CIBIC+ will be analyzed by analysis of variance (ANOVA), with effects in the model being investigator and treatment. Investigator-by-treatment interaction will be tested in a full model prior to conducting the primary ANCOVA or ANOVA (see description below).

\r\n

Because 3 treatment groups are involved, the primary analysis will be the test for linear dose response in the ANCOVA and ANOVA models described in the preceding paragraph. The result is then a single p-value for each of ADAS-Cog and CIBIC+.

\r\n

Analysis of the secondary efficacy variables will also be ANCOVA. Pairwise treatment comparisons of the adjusted means for all efficacy variables will be conducted using a LSMEANS statement within the GLM procedure.

\r\n

Investigator-by-treatment interaction will be tested in a full ANCOVA or ANOVA model, which takes the models described above, and adds the interaction term to the model. Interaction will be tested at α = .10 level. When the interaction is significant at this level, the data will be examined for each individual investigator to attempt to identify the source of the significant interaction. When the interaction is not significant, this term will be dropped from the model as described above, to test for investigator and treatment main effects. By doing so, all ANCOVA and ANOVA models will be able to validly test for treatment differences without weighting each investigator equally, which is what occurs when using Type III sums of squares (cell means model) with the interaction term present in the model. This equal weighting of investigators can become a serious problem when sample sizes are dramatically different between investigators.

\r\n

For all ANOVA and ANCOVA models, data collected from investigators who enrolled fewer than 3 patients in any one treatment group will be combined prior to analysis. If this combination still results in a treatment group having fewer than 3 patients in any one treatment group, then this group of patients will be combined with the next fewestenrolling investigator. In the event that there is a tie for fewest-enrolling investigator, one of these will be chosen at random by a random-number generator.

\r\n

The inherent assumption of normally distributed data will be evaluated by generating output for the residuals from the full ANCOVA and ANOVA models, which include the interaction term, and by testing for normality using the Shapiro-Wilk test from PROC UNIVARIATE. In the event that the data are predominantly nonnormally distributed, analyses will also be conducted on the ranked data. This rank transformation will be applied by ranking all the data for a particular variable, across all investigators and treatments, from lowest to highest. Integer ranks will be assigned starting at 1; mean ranks will be assigned when ties occur.

\r\n

In addition, the NPI-X will be analyzed in a manner similar to typical analyses of adverse events. In this analysis, each behavior will be considered individually. This analysis is referred to as “treatment-emergent signs and symptoms” (TESS) analysis. For each behavior, the patients will be dichotomized into 1 of 2 groups: those who experienced the behavior for the first time postrandomization, or those who had the quotient between frequency and severity increase relative to the baseline period defines one group. All other patients are in the second group. Treatments will be compared for overall differences by Cochran-Mantel-Haentzel (CMH) test referred to in SAS® as “row mean scores differ,” 2 degrees of freedom. The CMH correlation statistic (1 degree of freedom test), will test for increasing efficacy with increasing dose (trend test).

", + "

All comparisons between xanomeline and placebo with respect to efficacy variables should be one-sided. The justification for this follows.

\r\n

The statistical hypothesis that is tested needs to be consistent with the ultimate data-based decision that is reached. When conducting placebo-controlled trials, it is imperative that the drug be demonstrated to be superior in efficacy to placebo, since equivalent or worse efficacy than placebo will preclude approvability. Consequently, a one-sided test for efficacy is required.

\r\n

The null hypothesis is that the drug is equal or worse than placebo. The alternative hypothesis is that the drug has greater efficacy than placebo. A Type I error occurs only when it is concluded that a study drug is effective when in fact it is not. This can occur in only one tail of the distribution of the treatment difference. Further details of the arguments for one-sided tests in placebo-controlled trials are available in statistical publications (Fisher 1991; Koch 1991; Overall 1991; and Peace 1991).

\r\n

The argument for one-sided tests does not necessarily transfer to safety measures, in general, because one can accept a certain level of toxicity in the presence of strong efficacy. That is, safety is evaluated as part of a benefit/risk ratio.

\r\n

Note that this justification is similar to that used by regulatory agencies worldwide that routinely require one-sided tests for toxicological oncogenicity studies. In that case, the interest is not in whether a drug seems to lessen the occurrence of cancer; the interest is in only one tail of the distribution, namely whether the drug causes cancer to a greater extent than the control.

\r\n

Different regulatory agencies require different type I error rates. Treatment differences that are significant at the .025 α-level will be declared to be “statistically significant.” When a computed p-value falls between .025 and .05, the differences will be described as “marginally statistically significant.” This approach satisfies regulatory agencies who have accepted a one-sided test at the .05 level, and other regulatory agencies who have requested a two-sided test at the .05 level, or equivalently, a one-sided test at the .025 level. In order to facilitate the review of the final study report, two-sided p-values will be presented in addition to the one-sided p-values.

", + "

When there are multiple outcomes, and the study drug is declared to be effective when at least one of these outcomes achieves statistical significance in comparison with a placebo control, a downward adjustment to the nominal α-level is necessary. A well-known simple method is the Bonferroni method, that divides the overall Type I error rate, usually .05, by the number of multiple outcomes. So, for example, if there are two multiple outcomes, the study drug is declared to be effective if at least one of the two outcomes is significant at the .05/2 or .025 level.

\r\n

However, when one has the situation that is present in this study, where there are 2 (or 3 for Europe) outcome variables, each of which must be statistically significant, then the adjustment of the nominal levels is in the opposite direction, that is upwards, in order to maintain an overall Type 1 error rate of .05.

\r\n

In the case of two outcomes, ADAS-Cog (11) and CIBIC+, if the two variables were completely independent, then each variable should be tested at the nominal α-level of .05 1/2 = .2236 level. So if both variables resulted in a nominal p-value less than or equal to .2236, then we would declare the study drug to be effective at the overall Type 1 error rate of .05.

\r\n

We expect these two outcome measures to be correlated. From the first large-scale \r\nefficacy study of oral xanomeline, Study MC-H2Q-LZZA, the correlation between \r\nCIBIC+ and the change in ADAS-Cog(11) from baseline was .252. Consequently, we

\r\n

plan to conduct a randomization test to combine these two dependent dose-response p-values into a single test, which will then be at the .05 Type I error level. Because there will be roughly 300!/(3 * 100!) possible permutations of the data, random data permutations will be sampled (10,000 random permutations).

\r\n

Designate the dose response p-values as p1 and p2 (computed as one-sided p-values), for ADAS-Cog(11) and CIBIC+, respectively. The rejection region is defined as

\r\n

[ {p1 ≤ α and p2 ≤ α} ].

\r\n

The critical value, α, will be determined from the 10,000 random permutations by choosing the value of α to be such that 2.5% of the 10,000 computed pairs of dose response p-values fall in the rejection region. This will correspond to a one-sided test at the .025 level, or equivalently a two-sided test at the .05 level. In addition, by determining the percentage of permuted samples that are more extreme than the observed data, a single p-value is obtained.

", + "

Although safety data is collected at the 24 week visit for retrieved dropouts, these data will not be included in the primary analysis of safety.

\r\n

Pearson's chi-square test will be used to analyze 3 reasons for study discontinuation (protocol completed, lack of efficacy, and adverse event), the incidence of abnormal (high or low) laboratory measures during the postrandomization phase, and the incidence of treatment-emergent adverse events. The analysis of laboratory data is conducted by comparing the measures to the normal reference ranges (based on a large Lilly database), and counting patients in the numerator if they ever had a high (low) value during the postrandomization phase.

\r\n

Additionally, for the continuous laboratory tests, an analysis of change from baseline to endpoint will be conducted using the same ANOVA model described for the efficacy measures in Section 4.3. Because several laboratory analytes are known to be nonnormally distributed (skewed right), these ANOVAs will be conducted on the ranks.

\r\n

Several outcome measures will be extracted and analyzed from the Ambulatory ECG tapes, including number of pauses, QT interval, and AV block (first, second, or third degree). The primary consideration will be the frequency of pauses. The number of pauses greater than or equal to 2, 3, 4, 5 and 6 seconds will be tabulated. Primary analysis will focus on the number of pauses greater than or equal to 3 seconds. Due to possible outliers, these data will be analyzed as the laboratory data, by ANOVA on the ranks.

\r\n

Treatment-emergent adverse events (also referred to as treatment-emergent signs and symptoms, or TESS) are defined as any event reported during the postrandomization period (Weeks 0 - 26) that is worse in severity than during the baseline period, or one that occurs for the first time during the postrandomization period.

", + "

The effect of age, gender, origin, baseline disease severity as measured by MMSE, Apo E, and patient education level upon efficacy will be evaluated if sample sizes are sufficient to warrant such analyses. For example, if all patients are Caucasian, then there is no need to evaluate the co-factor origin. The ANCOVA and ANOVA models described above will be supplemented with terms for the main effect and interaction with treatment. Each co-factor will be analyzed in separate models. The test for treatment-bysubgroup interaction will address whether the response to xanomeline, compared with placebo, is different or consistent between levels of the co-factor.

", + "

Two interim efficacy analyses are planned. The first interim analysis will occur when approximately 50% of the patients have completed 8 weeks; the second interim analysis is to be conducted when approximately 50% of the patients have completed 24 weeks of the study. The purpose of these interim analyses is to provide a rationale for the initiation of subsequent studies of xanomeline TTS, or if the outcome is negative to stop development of xanomeline TTS. The method developed by Enas and Offen (1993) will be used as a guideline as to whether or not to stop one treatment arm, or the study, to declare ineffectiveness. The outcome of the interim analyses will not affect in any way the conduct, results, or analysis of the current study, unless the results are so negative that they lead to a decision to terminate further development of xanomeline TTS in AD. Hence, adjustments to final computed p-values are not appropriate.

\r\n

Planned interim analyses, and any unplanned interim analyses, will be conducted under the auspices of the data monitoring board assigned to this study. Only the data monitoring board is authorized to review completely unblinded interim efficacy and safety analyses and, if necessary, to disseminate those results. The data monitoring board will disseminate interim results only if absolutely necessary. Any such dissemination will be documented and described in the final study report. Study sites will not receive information about interim results unless they need to know for the safety of their patients.

", + "

An analysis of the cardiovascular safety monitoring (see section 3.9.4) will be performed when approximately 25 patients from each treatment arm have completed at least 2 weeks at the treatment arms' respective full dosage (Visit 5). If necessary, this analysis will be repeated every 25 patients per arm. This analysis will be conducted under the auspices of the DSMB. This board membership will be composed of 3 external cardiologists who will be the voting members of the board, a Lilly cardiologist, a Lilly statistician, and the Lilly research physician in charge of the study. Only the DSMB is authorized to review completely unblinded cardiovascular safety analyses and, if necessary, to disseminate those results. The outcome of the cardiovascular safety analyses will determine the need for further Ambulatory ECGs.

", + "

Plasma concentrations of xanomeline will be determined from samples obtained at selected visits (Section 3.9.2). The plasma concentration data for xanomeline, dosing information, and patient characteristics such as weight, gender and origin will be pooled and analyzed using a population pharmacokinetic analysis approach (for example, NONMEM). This approach preserves the individual pharmacokinetic differences through structural and statistical models. The population pharmacokinetic parameters through the structural model, and the interindividual and random residual variability through the components of the statistical models will be estimated. An attempt will also be made to correlate plasma concentrations with efficacy and safety data by means of population pharmacokinetic/pharmacodynamic modeling.

", + "
", + "

In the United States and Canada, the investigator is responsible for preparing the informed consent document. The investigator will use information provided in the current [Clinical Investigator's Brochure or product information] to prepare the informed consent document.

\r\n

The informed consent document will be used to explain in simple terms, before the patient is entered into the study, the risks and benefits to the patient. The informed consent document must contain a statement that the consent is freely given, that the patient is aware of the risks and benefits of entering the study, and that the patient is free to withdraw from the study at any time.

\r\n

As used in this protocol, the term “informed consent” includes all consent and/or assent given by subjects, patients, or their legal representatives.

\r\n

In addition to the elements required by all applicable laws, the 3 numbered paragraphs below must be included in the informed consent document. The language may be altered to match the style of the informed consent document, providing the meaning is unchanged. In some circumstances, local law may require that the text be altered in a way that changes the meaning. These changes can be made only with specific Lilly approval. In these cases, the ethical review board may request from the investigator documentation evidencing Lilly's approval of the language in the informed consent document, which would be different from the language contained in the protocol. Lilly shall, upon request, provide the investigator with such documentation.

\r\n
    \r\n
  1. “I understand that the doctors in charge of this study, or Lilly, may \r\nstop the study or stop my participation in the study at any time, for any \r\nreason, without my consent.”

  2. \r\n
  3. “I hereby give permission for the doctors in charge of this study to \r\nrelease the information regarding, or obtained as a result of, my \r\nparticipation in this study to Lilly, including its agents and contractors; \r\nthe US Food and Drug Administration (FDA) and other governmental \r\nagencies; and to allow them to inspect all my medical records. I \r\nunderstand that medical records that reveal my identity will remain \r\nconfidential, except that they will be provided as noted above or as \r\nmay be required by law.”

  4. \r\n
  5. “If I follow the directions of the doctors in charge of this study and I \r\nam physically injured because of any substance or procedure properly \r\ngiven me under the plan for this study, Lilly will pay the medical \r\nexpenses for the treatment of that injury which are not covered by my \r\nown insurance, by a government program, or by any other third party. \r\nNo other compensation is available from Lilly if any injury occurs.”

  6. \r\n
\r\n

The investigator is responsible for obtaining informed consent from each patient or legal representative and for obtaining the appropriate signatures on the informed consent document prior to the performance of any protocol procedures and prior to the administration of study drug.

", + "

The name and address of the ethical review board are listed on the Investigator/Contacts cover pages provided with this protocol.

\r\n

The investigator will provide Lilly with documentation of ethical review board approval of the protocol and the informed consent document before the study may begin at the site or sites concerned. The ethical review board(s) will review the protocol as required.

\r\n

The investigator must provide the following documentation:

\r\n
  • The ethical review board's annual reapproval of the protocol

  • \r\n
  • The ethical review board's approvals of any revisions to the informed \r\nconsent document or amendments to the protocol.

", + "

This study will be conducted in accordance with the ethical principles stated in the most recent version of the Declaration of Helsinki or the applicable guidelines on good clinical practice, whichever represents the greater protection of the individual.

\r\n

After reading the protocol, each investigator will sign 2 protocol signature pages and return 1 of the signed pages to a Lilly representative (see Attachment LZZT.10).

", + "
\r\n
\r\n
\r\n

Bierer LM, Haroutunian V, Gabriel S, Knott PJ, Carlin LS, Purohit DP, et al. 1995.
Neurochemical correlates of dementia severity in AD: Relative importance of the cholinergic deficits. J of Neurochemistry 64:749-760.

\r\n
\r\n
\r\n
\r\n
\r\n

Cummings JL, Mega M, Gray K, Rosenberg-Thompson S, et al. 1994. The Neuropsychiatric Inventory: Comprehensive assessment of psychopathology in dementia. Neurology 44:2308-2314.

\r\n
\r\n
\r\n
\r\n
\r\n

Enas GG, Offen WW. 1993. A simple stopping rule for declaring treatment ineffectiveness in clinical trials. J Biop Stat 3(1):13-32.

\r\n
\r\n
\r\n
\r\n
\r\n

Fisher A, Barak D. 1994. Promising therapeutic strategies in Alzheimer's disease based \r\non functionally selective M 1 muscarinic agonists. Progress and perspectives in new \r\nmuscarinic agonists. DN&P 7(8):453-464.

\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n

GLUCAGON for Injection ITO [Package Insert]. Osaka, Japan: Kaigen Pharma Co., Ltd; 2016.Available at:\r\n http://www.pmda.go.jp/PmdaSearch/iyakuDetail/ResultDataSetPDF/130616_7229400D1088_\r\n 1_11.

\r\n
\r\n
\r\n
\r\n
\r\n

Polonsky WH, Fisher L, Hessler D, Johnson N. Emotional distress in the partners of type 1diabetes adults:\r\n worries about hypoglycemia and other key concerns. Diabetes Technol Ther. 2016;18:292-297.

\r\n
\r\n
\r\n
\r\n
\r\n

Fisher LD. 1991. The use of one-sided tests in drug trials: an FDA advisory committee \r\nmember's perspective. J Biop Stat 1:151-6.

\r\n
\r\n
\r\n
\r\n
\r\n

Koch GG. 1991. One-sided and two-sided tests and p-values. J Biop Stat 1:161-70.

\r\n
\r\n
\r\n
\r\n
\r\n

Overall JE. 1991. A comment concerning one-sided tests of significance in new drug \r\napplications. J Biop Stat 1:157-60.

\r\n
\r\n
\r\n
\r\n
\r\n

Peace KE. 1991. Oneside or two-sided p-values: which most appropriately address the \r\nquestion of drug efficacy? J Biop Stat 1:133-8.

\r\n
\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The following SoA timelines are auto generated using the detailed study design held within the USDM.

\r\n
\r\n

Timeline: Main Timeline, Potential subject identified

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X1

X

X

X

X

X

X

X

X

X

X

X

X2

X

X

X

X

X3

X

X

X

X

X4

X

X

X

X

X5

X

X

X

X

X

X

X

X

X

X

X

X

X

X

1

Performed if patient is an insulin-dependent diabetic

2

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

3

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

4

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

5

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

Timeline: Adverse Event Timeline, Subject suffers an adverse event

X

Timeline: Early Termination Timeline, Subject terminates the study early

X

", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "
\r\n
\r\n

Note:

\r\n

The attachment has not been included in this issue of the protocol. It may be included in future versions.

\r\n
\r\n
", + "

Sponsor Confidentiality Statement:

Full Title:

Trial Acronym:

Protocol Identifier:

Original Protocol:

Version Number:

Version Date:

Amendment Identifier:

Amendment Scope:

Compound Codes(s):

Compound Name(s):

Trial Phase:

Short Title:

Sponsor Name and Address:

,

Regulatory Agency Identifier Number(s):

Spondor Approval Date:

", + "
Committees\r\n

A Data Safety Monitoring Board (DSMB), chaired by an external cardiologist, will meet after 75, 150, 225, and 300 patients have completed 1 month of treatment. The DSMB will review cardiovascular findings to decide if discontinuation of the study or any treatment arm is appropriate, if additional cardiovascular monitoring is required, if further cardiovascular monitoring is unnecessary, or if adjustment of dose within a treatment arm (or arms) is appropriate (see Section 3.9.4).

", + "
\"Alt\r\n

Figure LZZT.1. Illustration of study design for Protocol H2Q-MC-LZZT(c).

\r\n

Following informed consent, patients will be screened at Visit 1. At screening, patients will undergo complete neuropsychiatric assessment, psychometric testing, and general medical assessment (including medical history, pre-existing conditions, physical examination). In addition, vital signs, temperature, medication history, electrocardiogram (ECG), chest x-ray, and safety laboratories will be obtained. During the screening visit, patients will wear a placebo TTS to determine willingness and ability to comply with transdermal administration procedures. If patients have not had central nervous system (CNS) imaging in the previous 12 months, a computed tomography (CT) or magnetic resonance imaging (MRI) scan will be obtained. If patients are insulin dependent diabetics, a hemoglobin A 1c will be obtained. Screening exams and procedures may be performed after Visit 1; however, their results must be completed and available prior to randomization. The screening process should occur within 2 weeks of randomization (Visit 3 of the study).

\r\n

Patients who meet enrollment criteria from Visit 1 will proceed to Visit 2 at which time they will undergo a 24-hour Ambulatory ECG. At Visit 3 the Ambulatory ECG will be removed and patients will be randomized to 1 of 3 treatment arms. The treatment arms will include a placebo arm, a low-dose xanomeline arm (50 cm 2 TTS Formulation E, 54 mg xanomeline), and a high-dose xanomeline arm (75 cm 2 TTS Formulation E, 81 mg xanomeline). All patients receiving xanomeline will be started at 50 cm 2 TTS Formulation E. For the first 8 weeks of treatment, patients will be assessed at clinic visits every 2 weeks and, thereafter, at clinic visits every 4 weeks. Patients who discontinue prior to Visit 12 (Week 24) will be brought back for full efficacy assessments at or near to 24 weeks, whenever possible.

\r\n

At Visits 3, 8, 10, and 12, efficacy instruments (ADAS-Cog, CIBIC+, and DAD) will be administered. NPI-X will be administered at 2-week intervals either at clinic visits or via a telephone interview. Vital signs, temperature, and an assessment of adverse events will be obtained at all clinic visits. An electrocardiogram (ECG), and chemistry/hematology safety labs will be obtained at Visits 4, 5, 7, 8, 9, 10, 11, 12, and 13. Urinalysis will be done at Visits 4, 9, and 12. Use of concomitant medications will be collected at Visits 3, 4, 5, 7, 8, 9, 10, 11, 12, and 13. Plasma levels of xanomeline and metabolites will be obtained at Visits 3, 4, 5, 7, 9, and 11. At Visits 3, 4, 5, 7, 8, 9, 10, 11, and 12, medications will be dispensed to the patients.

\r\n

Visits 1 through 13 should be scheduled relative to Visit 3 (Week 0 - randomization). Visits 4, 5, 7, 8, and 13 should occur within 3 days of their scheduled date. Visits 9, 10, 11, and 12 should occur within 4 days of their scheduled date. At Visit 13 patients will be given the option to enter the open-label extension phase (see Section 3.10.3. Study Extensions).

", + "
\r\n
\r\n

Note:

\r\n

The following SoA timelines are auto generated using the detailed study design held within the USDM.

\r\n
\r\n

Timeline: Main Timeline, Potential subject identified

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X

X1

X

X

X

X

X

X

X

X

X

X

X

X2

X

X

X

X

X3

X

X

X

X

X4

X

X

X

X

X5

X

X

X

X

X

X

X

X

X

X

X

X

X

X

1

Performed if patient is an insulin-dependent diabetic

2

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

3

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

4

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

5

Practice only - It is recommended that a sampling of the CIBIC+, ADAS-Cog, DAD, and NPI-X be administered at Visit 1. Data from this sampling would not be considered as study data and would not be collected.

Timeline: Adverse Event Timeline, Subject suffers an adverse event

X

Timeline: Early Termination Timeline, Subject terminates the study early

X

", + "

The primary objectives of this study are

\r\n
    \r\n
  • \r\n
  • \r\n
", + "

The secondary objectives of this study are

\r\n
    \r\n
  • \r\n
  • \r\n
  • \r\n
  • \r\n
", + "

Approximately 300 patients will be enrolled (see Schedule of Events for Protocol H2Q-MC-LZZT(c), Attachment LZZT.1).

\r\n

Duration

\r\n

SOMETHING HERE

\r\n

Patients with probable mild to moderate AD will be studied in a randomized, double-blind, parallel (3 arm), placebo-controlled trial of 26 weeks duration. The study will be conducted on an outpatient basis.

\r\n

At Visit 1, patients who meet the enrollment criteria of Mini-Mental State Examination (MMSE) score of 10 to 23 (Attachment LZZT.6), Hachinski Ischemia Score ≤4 (Attachment LZZT.8), a physical exam, safety labs, ECG, and urinalysis, will proceed to Visit 2 and Visit 3. At Visit 3, patients whose CNS imaging and other pending labs from Visit 1 satisfy the inclusion criteria (Section 3.4.2.1) will be enrolled in the study. Approximately 300 patients with a diagnosis of probable mild to moderate AD will be enrolled in the study.

", + "

Patients may be included in the study only if they meet all the following criteria:

\r\n
01
02
03
04
05
06
07
08
", + "

Patients will be excluded from the study for any of the following reasons:

\r\n
09
10
11
12
13
14
15
16b
17
18
19
20
21
22
23
24
25
26
27b
28b
29b
30b
31b
" + ], + "instanceType": [ + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem", + "NarrativeContentItem" + ] + } + } + ], + "codelists": [] +} diff --git a/tests/resources/CoreIssue897/Rule.yml b/tests/resources/CoreIssue897/Rule.yml new file mode 100644 index 000000000..03bdb4f0d --- /dev/null +++ b/tests/resources/CoreIssue897/Rule.yml @@ -0,0 +1,40 @@ +Authorities: + - Organization: CDISC + Standards: + - Name: USDM + References: + - Citations: + - Cited Guidance: "Narrative content item text is expected to be HTML formatted." + Document: "USDM_CORE_Rules.xlsx" + Origin: "USDM Conformance Rules" + Rule Identifier: + Id: "DDF00187" + Version: "1" + Version: "1.0" + Version: "4.0" +Check: + all: + - name: $xhtml_errors + operator: non_empty +Core: + Id: "CORE-000409" + Status: Draft + Version: "1" +Description: "Narrative content item text is expected to be HTML formatted." +Executability: Partially Executable - Possible Overreporting +Operations: + - id: $xhtml_errors + name: text + operator: get_xhtml_errors + namespace: http://www.cdisc.org/ns/usdm/xhtml/v1.0 +Outcome: + Message: "The narrative content item text contains non-conformant XHTML." + Output Variables: + - text + - $xhtml_errors +Rule Type: Record Data +Scope: + Entities: + Include: + - "NarrativeContentItem" +Sensitivity: Record diff --git a/tests/unit/test_operations/test_get_xhtml_errors.py b/tests/unit/test_operations/test_get_xhtml_errors.py new file mode 100644 index 000000000..a61a9b4a3 --- /dev/null +++ b/tests/unit/test_operations/test_get_xhtml_errors.py @@ -0,0 +1,90 @@ +from typing import Any +from unittest.mock import MagicMock + +import pandas as pd +import pytest + +from cdisc_rules_engine.exceptions.custom_exceptions import SchemaNotFoundError +from cdisc_rules_engine.models.dataset import PandasDataset +from cdisc_rules_engine.models.operation_params import OperationParams +from cdisc_rules_engine.operations.get_xhtml_errors import GetXhtmlErrors + + +@pytest.mark.parametrize( + "target_column, dataset, namespace, expected", + [ + ( # column is not in the dataset + "target", + PandasDataset.from_records( + [ + {"column": ""}, + {"column": ""}, + {"column": ""}, + ] + ), + "http://www.cdisc.org/ns/usdm/xhtml/v1.0", + KeyError, + ), + ( # schema violation + "target", + PandasDataset.from_records( + [ + { + "target": '

Table LZZT.1 lists the clinical laboratory tests that will be performed at Visit 1.

\r\n

Table LZZT.1. Laboratory Tests Performed at Admission (Visit 1)

\r\n\r\n

Safety Laboratory Tests

\r\n\r\n\r\n\r\n\r\n\r\n
\r\n

Hematology:

\r\n

    \r\n
  • Hemoglobin
  • \r\n
  • Hematocrit
  • \r\n
  • Erythrocyte count (RBC)
  • \r\n
  • Mean cell volume (MCV)
  • \r\n
  • Mean cell hemoglobin (MCH)
  • \r\n
  • Mean cell hemoglobin concentration (MCHC)
  • \r\n
  • Leukocytes (WBC)
  • \r\n
  • Neutrophils, segmented
  • \r\n
  • Neutrophils, juvenile (bands)
  • \r\n
  • Lymphocytes
  • \r\n
  • Monocytes
  • \r\n
  • Eosinophils
  • \r\n
  • Basophils
  • \r\n
  • Platelet
  • \r\n
  • Cell morphology
  • \r\n

\r\n

Urinalysis:

\r\n

    \r\n
  • Color
  • \r\n
  • Specific gravity
  • \r\n
  • pH
  • \r\n
  • Protein
  • \r\n
  • Glucose
  • \r\n
  • Ketones
  • \r\n
  • Bilirubin
  • \r\n
  • Urobilinogen
  • \r\n
  • Blood
  • \r\n
  • Nitrite
  • \r\n
  • Microscopic examination of sediment
  • \r\n

\r\n
\r\n

Clinical Chemistry - Serum Concentration of:

\r\n

    \r\n
  • Sodium
  • \r\n
  • Potassium
  • \r\n
  • Bicarbonate
  • \r\n
  • Total bilirubin
  • \r\n
  • Alkaline phosphatase (ALP)
  • \r\n
  • Gamma-glutamyl transferase (GGT)
  • \r\n
  • Alanine transaminase (ALT/SGPT)
  • \r\n
  • Aspartate transaminase (AST/SGOT)
  • \r\n
  • Blood urea nitrogen (BUN)
  • \r\n
  • Serum creatinine
  • \r\n
  • Uric acid
  • \r\n
  • Phosphorus
  • \r\n
  • Calcium
  • \r\n
  • Glucose, nonfasting
  • \r\n
  • Total protein
  • \r\n
  • Albumin
  • \r\n
  • Cholesterol
  • \r\n
  • Creatine kinase (CK)
  • \r\n

\r\n

Thyroid Function Test (Visit 1 only):

\r\n
    \r\n
  • Free thyroid index
  • \r\n
  • T3 Uptake
  • \r\n
  • T4
  • \r\n
  • Thyroid-stimulating hormone (TSH)
  • \r\n
\r\n

Other Tests (Visit 1 only):

\r\n
    \r\n
  • Folate
  • \r\n
  • Vitamin B 12
  • \r\n
  • Syphilis screening
  • \r\n
  • Hemoglobin A1C (IDDM patients only)
\r\n
\r\n

Laboratory values that fall outside a clinically accepted reference range or values that differ significantly from previous values must be evaluated and commented on by the investigator by marking CS (for clinically significant) or NCS (for not clinically significant) next to the values. Any clinically significant laboratory values that are outside a clinically acceptable range or differ importantly from a previous value should be further commented on in the clinical report form comments page.

\r\n

Hematology, and clinical chemistry will also be performed at Visits 4, 5, 7, 8, 9, 10, 11, 12, and 13. Patients that experience a rash and/or eosinophilia may have additional hematology samples obtained as described in 3.9.3.4 (Other Safety Measures).

\r\n

Urinalysis will also be performed at Visits 4, 9, and 12. The following criteria have been developed to monitor hepatic function.

\r\n
    \r\n
  • Patients with ALT/SGPT levels >120 IU will be retested weekly.

    \r\n
  • Patients with ALT/SGPT values >400 IU, or alternatively, an elevated ALT/SGPT accompanied by GGT and/or ALP values >500 IU will be retested within 2 days. The sponsor\'s clinical research administrator or clinical research physician is to be notified. If the retest value does not decrease by at least 10%, the study drug will be discontinued; additional laboratory tests will be performed until levels return to normal. If the retest value does decrease by 10% or more, the study drug may be continued with monitoring at 3 day intervals until ALT/SGPT values decrease to <400 IU or GGT and/or ALP values decrease to <500 IU. \r\n

' # noqa: E501 + }, + ] + ), + "http://www.cdisc.org/ns/usdm/xhtml/v1.0", + [ + [ + "Invalid XHTML line 3 [ERROR]: Element 'style': This element is not expected." + ] + ], + ), + ( # valid dataset + "target", + PandasDataset.from_records( + [ + { + "target": '

Table LZZT.1 lists the clinical laboratory tests that will be performed at Visit 1.

\r\n

Table LZZT.1. Laboratory Tests Performed at Admission (Visit 1)

\r\n

Safety Laboratory Tests

\r\n\r\n\r\n\r\n\r\n\r\n
\r\n

Hematology:

\r\n

\r\n

Urinalysis:

\r\n

\r\n
\r\n

Clinical Chemistry - Serum Concentration of:

\r\n

\r\n

Thyroid Function Test (Visit 1 only):

\r\n

Other Tests (Visit 1 only):

\r\n
\r\n

Laboratory values that fall outside a clinically accepted reference range or values that differ significantly from previous values must be evaluated and commented on by the investigator by marking CS (for clinically significant) or NCS (for not clinically significant) next to the values. Any clinically significant laboratory values that are outside a clinically acceptable range or differ importantly from a previous value should be further commented on in the clinical report form comments page.

\r\n

Hematology, and clinical chemistry will also be performed at Visits 4, 5, 7, 8, 9, 10, 11, 12, and 13. Patients that experience a rash and/or eosinophilia may have additional hematology samples obtained as described in 3.9.3.4 (Other Safety Measures).

\r\n

Urinalysis will also be performed at Visits 4, 9, and 12. The following criteria have been developed to monitor hepatic function.

\r\n
' # noqa: E501 + }, + ] + ), + "http://www.cdisc.org/ns/usdm/xhtml/v1.0", + [[]], + ), + ( # invalid namespace + "target", + PandasDataset.from_records( + [ + { + "target": '

Table LZZT.1 lists the clinical laboratory tests that will be performed at Visit 1.

\r\n

Table LZZT.1. Laboratory Tests Performed at Admission (Visit 1)

\r\n

Safety Laboratory Tests

\r\n\r\n\r\n\r\n\r\n\r\n
\r\n

Hematology:

\r\n

\r\n

Urinalysis:

\r\n

\r\n
\r\n

Clinical Chemistry - Serum Concentration of:

\r\n

\r\n

Thyroid Function Test (Visit 1 only):

\r\n

Other Tests (Visit 1 only):

\r\n
\r\n

Laboratory values that fall outside a clinically accepted reference range or values that differ significantly from previous values must be evaluated and commented on by the investigator by marking CS (for clinically significant) or NCS (for not clinically significant) next to the values. Any clinically significant laboratory values that are outside a clinically acceptable range or differ importantly from a previous value should be further commented on in the clinical report form comments page.

\r\n

Hematology, and clinical chemistry will also be performed at Visits 4, 5, 7, 8, 9, 10, 11, 12, and 13. Patients that experience a rash and/or eosinophilia may have additional hematology samples obtained as described in 3.9.3.4 (Other Safety Measures).

\r\n

Urinalysis will also be performed at Visits 4, 9, and 12. The following criteria have been developed to monitor hepatic function.

\r\n
' # noqa: E501 + }, + ] + ), + "invalid-namespace", + SchemaNotFoundError, + ), + ], +) +def test_get_xhtml_errors( + target_column: str, + dataset: PandasDataset, + namespace: str, + expected: Any, + operation_params: OperationParams, +): + operation_id = "$get_xhtml_errors" + operation_params.operation_id = operation_id + operation_params.namespace = namespace + operation = GetXhtmlErrors( + params=operation_params, + original_dataset=dataset, + cache_service=MagicMock(), + data_service=MagicMock(), + ) + try: + result = operation._execute_operation() + except Exception as e: + result = pd.Series(type(e)) + assert result.equals(pd.Series(expected))