EMA Write PMS API Implementation Guide - Enrichments
1.2.0 - ci-build

EMA Write PMS API Implementation Guide - Enrichments - Local Development build (v1.2.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Resource Profile: EMA Write API Marketing Regulated Authorization

Official URL: http://ema.europa.eu/fhir/StructureDefinition/emaWriteApiRegulatedAuthorizationRestrictions Version: 1.2.0
Draft as of 2025-08-08 Computable Name: EmaWriteApiRegulatedAuthorizationRestrictions

Defines the rule a Marketing RegulatedAuthorization resource instance must conform to when belonging to a FHIR bundle representing a Human Variation Application

Usage:

Formal Views of Profile Content

Description of Profiles, Differentials, Snapshots and how the different presentations work.

NameFlagsCard.TypeDescription & Constraintsdoco
.. RegulatedAuthorization 0..* RegulatedAuthorization Regulatory approval, clearance or licencing related to a regulated product, treatment, facility or activity e.g. Market Authorization for a Medicinal Product
dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources
dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
dom-5: If a resource is contained in another resource, it SHALL NOT have a security label
dom-6: A resource should have narrative for robust management

doco Documentation for this format

This structure is derived from RegulatedAuthorization

NameFlagsCard.TypeDescription & Constraintsdoco
.. RegulatedAuthorization RegulatedAuthorization
... meta 0..0
... implicitRules 0..0
... language 0..0
... contained 0..0
... modifierExtension 0..0
... description 0..0
... indication 0..0
... intendedUse 0..0
... basis 0..0

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. RegulatedAuthorization 0..* RegulatedAuthorization Regulatory approval, clearance or licencing related to a regulated product, treatment, facility or activity e.g. Market Authorization for a Medicinal Product
... id Σ 0..1 id Logical id of this artifact
... extension 0..* Extension Additional content defined by implementations
... identifier Σ 0..* Identifier Business identifier for the authorization, typically assigned by the authorizing body
... type Σ 0..1 CodeableConcept Overall type of this authorization, for example drug marketing approval, orphan drug designation
Binding: RegulatedAuthorizationType (example): Overall type of this authorization.

... region Σ 0..* CodeableConcept The territory in which the authorization has been granted
Binding: JurisdictionValueSet (example): Jurisdiction codes


... status Σ 0..1 CodeableConcept The status that is authorised e.g. approved. Intermediate states can be tracked with cases and applications
Binding: PublicationStatus (preferred): The lifecycle status of an artifact.

... statusDate Σ 0..1 dateTime The date at which the current status was assigned
... validityPeriod Σ 0..1 Period The time period in which the regulatory approval etc. is in effect, e.g. a Marketing Authorization includes the date of authorization and/or expiration date
... holder Σ 0..1 Reference(Organization) The organization that has been granted this authorization, by the regulator
... regulator Σ 0..1 Reference(Organization) The regulatory authority or authorizing body granting the authorization
... attachedDocument Σ 0..* Reference(DocumentReference) Additional information or supporting documentation about the authorization
... case Σ 0..1 BackboneElement The case or regulatory procedure for granting or amending a regulated authorization. Note: This area is subject to ongoing review and the workgroup is seeking implementer feedback on its use (see link at bottom of page)
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... identifier Σ 0..1 Identifier Identifier by which this case can be referenced
.... type Σ 0..1 CodeableConcept The defining type of case
Binding: RegulatedAuthorizationCaseType (example): The type of a case involved in an application.

.... status Σ 0..1 CodeableConcept The status associated with the case
Binding: PublicationStatus (preferred): The lifecycle status of an artifact.

.... date[x] Σ 0..1 Relevant date for this case
..... datePeriod Period
..... dateDateTime dateTime
.... application Σ 0..* See case (RegulatedAuthorization) Applications submitted to obtain a regulated authorization. Steps within the longer running case or procedure

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
RegulatedAuthorization.typeexampleRegulatedAuthorizationType
http://hl7.org/fhir/ValueSet/regulated-authorization-type
from the FHIR Standard
RegulatedAuthorization.regionexampleJurisdictionValueSet
http://hl7.org/fhir/ValueSet/jurisdiction
from the FHIR Standard
RegulatedAuthorization.statuspreferredPublicationStatus
http://hl7.org/fhir/ValueSet/publication-status
from the FHIR Standard
RegulatedAuthorization.case.typeexampleRegulatedAuthorizationCaseType
http://hl7.org/fhir/ValueSet/regulated-authorization-case-type
from the FHIR Standard
RegulatedAuthorization.case.statuspreferredPublicationStatus
http://hl7.org/fhir/ValueSet/publication-status
from the FHIR Standard

This structure is derived from RegulatedAuthorization

Summary

Prohibited: 10 elements

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. RegulatedAuthorization 0..* RegulatedAuthorization Regulatory approval, clearance or licencing related to a regulated product, treatment, facility or activity e.g. Market Authorization for a Medicinal Product
dom-2: If the resource is contained in another resource, it SHALL NOT contain nested Resources
dom-3: If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
dom-4: If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
dom-5: If a resource is contained in another resource, it SHALL NOT have a security label
dom-6: A resource should have narrative for robust management

doco Documentation for this format

Differential View

This structure is derived from RegulatedAuthorization

NameFlagsCard.TypeDescription & Constraintsdoco
.. RegulatedAuthorization RegulatedAuthorization
... meta 0..0
... implicitRules 0..0
... language 0..0
... contained 0..0
... modifierExtension 0..0
... description 0..0
... indication 0..0
... intendedUse 0..0
... basis 0..0

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. RegulatedAuthorization 0..* RegulatedAuthorization Regulatory approval, clearance or licencing related to a regulated product, treatment, facility or activity e.g. Market Authorization for a Medicinal Product
... id Σ 0..1 id Logical id of this artifact
... extension 0..* Extension Additional content defined by implementations
... identifier Σ 0..* Identifier Business identifier for the authorization, typically assigned by the authorizing body
... type Σ 0..1 CodeableConcept Overall type of this authorization, for example drug marketing approval, orphan drug designation
Binding: RegulatedAuthorizationType (example): Overall type of this authorization.

... region Σ 0..* CodeableConcept The territory in which the authorization has been granted
Binding: JurisdictionValueSet (example): Jurisdiction codes


... status Σ 0..1 CodeableConcept The status that is authorised e.g. approved. Intermediate states can be tracked with cases and applications
Binding: PublicationStatus (preferred): The lifecycle status of an artifact.

... statusDate Σ 0..1 dateTime The date at which the current status was assigned
... validityPeriod Σ 0..1 Period The time period in which the regulatory approval etc. is in effect, e.g. a Marketing Authorization includes the date of authorization and/or expiration date
... holder Σ 0..1 Reference(Organization) The organization that has been granted this authorization, by the regulator
... regulator Σ 0..1 Reference(Organization) The regulatory authority or authorizing body granting the authorization
... attachedDocument Σ 0..* Reference(DocumentReference) Additional information or supporting documentation about the authorization
... case Σ 0..1 BackboneElement The case or regulatory procedure for granting or amending a regulated authorization. Note: This area is subject to ongoing review and the workgroup is seeking implementer feedback on its use (see link at bottom of page)
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... identifier Σ 0..1 Identifier Identifier by which this case can be referenced
.... type Σ 0..1 CodeableConcept The defining type of case
Binding: RegulatedAuthorizationCaseType (example): The type of a case involved in an application.

.... status Σ 0..1 CodeableConcept The status associated with the case
Binding: PublicationStatus (preferred): The lifecycle status of an artifact.

.... date[x] Σ 0..1 Relevant date for this case
..... datePeriod Period
..... dateDateTime dateTime
.... application Σ 0..* See case (RegulatedAuthorization) Applications submitted to obtain a regulated authorization. Steps within the longer running case or procedure

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
RegulatedAuthorization.typeexampleRegulatedAuthorizationType
http://hl7.org/fhir/ValueSet/regulated-authorization-type
from the FHIR Standard
RegulatedAuthorization.regionexampleJurisdictionValueSet
http://hl7.org/fhir/ValueSet/jurisdiction
from the FHIR Standard
RegulatedAuthorization.statuspreferredPublicationStatus
http://hl7.org/fhir/ValueSet/publication-status
from the FHIR Standard
RegulatedAuthorization.case.typeexampleRegulatedAuthorizationCaseType
http://hl7.org/fhir/ValueSet/regulated-authorization-case-type
from the FHIR Standard
RegulatedAuthorization.case.statuspreferredPublicationStatus
http://hl7.org/fhir/ValueSet/publication-status
from the FHIR Standard

This structure is derived from RegulatedAuthorization

Summary

Prohibited: 10 elements

 

Other representations of profile: CSV, Excel, Schematron