Skip to main content

RegulatedAuthorizationCase

Regulatory approval, clearance or licencing related to a regulated product, treatment, facility or activity that is cited in a guidance, regulation, rule or legislative act. An example is Market Authorization relating to a Medicinal Product.

type RegulatedAuthorizationCase implements Element {
  identifier: Identifier
  type: CodeableConcept
  status: CodeableConcept
  datePeriod: Period
  dateDateTime: Date
  application: [RegulatedAuthorizationCase]
  modifierExtension: [Extension]
  extension: [Extension]
  id: String
}

Fields​

RegulatedAuthorizationCase.identifier ● Identifier object​

Identifier by which this case can be referenced.

RegulatedAuthorizationCase.type ● CodeableConcept object​

The defining type of case.

RegulatedAuthorizationCase.status ● CodeableConcept object​

The status associated with the case.

RegulatedAuthorizationCase.datePeriod ● Period object​

Relevant date for this case. (choose any one of date*, but only one)

RegulatedAuthorizationCase.dateDateTime ● Date scalar​

Relevant date for this case. (choose any one of date*, but only one)

RegulatedAuthorizationCase.application ● [RegulatedAuthorizationCase] list object​

A regulatory submission from an organization to a regulator, as part of an assessing case. Multiple applications may occur over time, with more or different information to support or modify the submission or the authorization. The applications can be considered as steps within the longer running case or procedure for this authorization process.

RegulatedAuthorizationCase.modifierExtension ● [Extension] list object​

May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element s descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions. Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).

RegulatedAuthorizationCase.extension ● [Extension] list object​

May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.

RegulatedAuthorizationCase.id ● String scalar​

Interfaces​

Element interface​

Base definition for all elements in a resource. If the element is present, it must have a value for at least one of the defined elements, an @id referenced from the Narrative, or extensions

Member Of​

RegulatedAuthorization object ● RegulatedAuthorizationCase object