| − | <H2>3 Application</H2> <p>Note that the term application is not used here with the same meaning as given in the HL7 glossary. In RPS an application is a collection of documents and metadata concerning a product regulated by approval, both submitted to a regulatory authority, and returned by the regulator as responses. An application is the highest level of content organization recognized in RPS. It is subdivided into submissions, which may themselves be further subdivided into reviewable units.</p> <p>Submission Message Term: application</p> <H2>6 Application life Cycle</H2> <p> [tbd]</p> <p>Submission Message Term: application – status code ?</p> <H2>15 code set</H2> <p>see shared controlled vocabulary</p> <H2>16 code system</H2> <p>see shared controlled vocabulary</p> <H2>18 Filing order</H2> <p>documents are virtually filed under specified headings in a standardized table of contents for the particular application type. (By virtually filed, we mean displayed under those headings by the software tools used to access and manage the document databases). The heading is specified by a context of use that also references the document. Since more than one document may file under the same heading, a secondary sorting order may be specified by, first type and value of any keywords associated with the document or context of use (?), and then by a numerical position value associated with the context of use. The numerical position is specified as a positive real number so that a context of use may <p>Submission Message Term: component 1 – priority number</p> <H2>23 Context of use</H2> <p> a context of use associates one document with a position in a standardized table of contents defined by a controlled vocabulary. A context of use has a life cycle.</p> <p>Submission Message Term: context of use</p> <H2>24 Context of use, derivation</H2> <p>:a context of use is said to be derived from a document in that the attribute values and associated keywords used when processing it may be inherited from the document.</p> <H2>26 Context of use code</H2> <p>the context of use code is a value taken from a shared controlled vocabulary representing the ordered headings of a standardized table of contents for a given kind of application. The code determines the heading under which the document is virtually filed. (A given document can be virtually filed in multiple locations by reference from different context of use instances.)</p> <p>Submission Message Term: Context of use – code</p> <H2>28 Context of use life cycle</H2> <p> [tbd]</p> <p>Submission Message Term: Context of use – status code</p> <H2>34 Document</H2> <p>a document is the unit of content managed by RPS. A document object is created once with a unique id and may be referenced from any number of other documents or context of uses . A document has a life <p>Submission Message Term: document </p> <H2>35 Document, simple</H2> <p>a simple document comprises exactly one file, which must accompany the RPS message in which the document object is submitted; the file is referenced by path and name in the document object. Each file accompanying an RPS message must be referenced from exactly one simple document object.</p> <H2>36 Document, compound</H2> <p>a compound document comprises one or more simple and/or compound document, which are referenced by id as components.</p> <H2>39 Document type</H2> <p>documents may be assigned a type from a shared controlled vocabulary. It is expected that a controlled vocabulary will be published by ICH for study documents; other regulators may develop controlled vocabularies for other purposes.</p> <p>Submission Message Term: Document – code</p> <H2>42 Document life cycle</H2> <p>[tbd]</p> <p>Submission Message Term: Document – status code</p> <H2>46 File</H2> <p> The actual content of submissions is provided electronically in named digital files of various formats, as dictated by the regulator’s policies. Files are submitted in batches along with an RPS message. Each file is to be submitted exactly once, and referenced from exactly one document object in the <H2>50 Keyword application</H2> <p> keywords are applied to (i.e. used on) document or context of use instances by associating either a keyword definition by reference to its id, or a keyword name and value directly from a controlled vocabulary by using the appropriate code.</p> <p>Submission Message Term: keyword</p> <H2>53 Keyword, use life cycle</H2> <p> when a keyword used on a document or context of use is to be replaced or dropped then a new version of the document or context of use instance is submitted, including the whole new set of keywords applied to that instance.</p> <p>Submission Message Term: keyword - status code</p> <H2>54 Keyword</H2> <p>a keyword is a name-value pair, where the name identifies the type of keyword, and the value is a text string to be used on a document or context of use to which that keyword is applied. Keywords are applied to (i.e. used on) document and content of use instances as additional metadata to modify their retrieval, <p>Submission Message Term: keyword definition</p> <H2>55 Keyword sources</H2> <p> keywords may be invoked directly from a shared controlled vocabulary, or may be defined in and for an application. Keywords that are defined in and for an application are subject to a managed life cycle.</p> <H2>58 Keyword definition life cycle</H2> <p>once a keyword has been defined in and for an application, it may be replaced (i.e. assigned a new type and/or value) or it may dropped entirely from further use. In either case a new keyword definition is submitted with a reference to the keyword definition being replaced.</p> <p>Submission Message Term: keyword definition - status code</p> <H2>59 Keyword definition</H2> <p>a keyword may be defined in and for an application by specifying its type from a controlled vocabulary and assigning it a text string value.</p> <p>Submission Message Term: keyword definition – value</p> <H2>68 Context of use, multiple application</H2> <p> a context of use applies in each reviewable unit and/or submission to which the submission unit of which it is a component pertains.</p> <p>Submission Message Term: pertinent information3</p> <H2>69 Context of use, multiple application exclusions</H2> <p> the application of a context of use may be excluded from an identified submission(s) in a multiple application situation.</p> <H2>101 Shared controlled vocabulary</H2> <p> a shared controlled vocabulary is an encoded knowledge representation that is used to classify RPS information objects in some domain. It is sometimes also called a code set or a code system. Within the HL7 formalism a given vocabulary must be identified by an OID, and contain a set of entries, each with a code value and a display text string. A given vocabulary may have other information associated with each entry to assist its users in applying and managing codes, including information concerning the ordering, nesting and/or association of entries.It is shared by virtue of its being published and available from an authoritative source. Shared vocabularies needed for RPS include context of use code sets, document type code sets, user-definable keyword type code sets, and pre-defined keyword code sets.</p> <p>Submission Message Term: Shared controlled vocabulary</p> <H2>109 Submission</H2> <p> a submission is a organizational subdivision of an application, usually associated with a specific regulatory activity or purpose.</p> <p>Submission Message Term: submission</p> <H2>112 Submission, withdrawal</H2> <p>when a sponsor wishes to withdraw a submission they submit a empty submission unit pertaining to a submission with the same id value and the status code set to null.</p> <p>Submission Message Term: submission – status code</p> <H2>117 Submission unit</H2> <p> a submission unit is the portion of an RPS message that carries the organizational and management metadata applicable to the batch of files accompanying the unit or to documents previously submitted. It may be sent as a submission by the applicant or as a response form the regulator.</p> <p>Submission Message Term: submission unit</p> <H2>121 Submission unit, withdrawal</H2> <p> when a sponsor wishes to withdraw a submission unit they submit an empty submission unit with the same id value and the status code set to null</p> <p>Submission Message Term: submission unit - status code</p>
| |
