Generated Narrative: StructureDefinition ch-idmp-regulatedauthorization Name Flags Card. Type Description & Constraints<img src="[binary]" alt="doco" style="background-color: inherit"/> RegulatedAuthorization 0..* RegulatedAuthorization RegulatedAuthorization #xD; subject 0..* Reference(MedicinalProductDefinition | PackagedProductDefinition | ManufacturedItemDefinition | Ingredient) The product type, treatment, facility or activity that is being authorized #xD; type 0..1 CodeableConcept Overall type of this authorization, for example drug marketing approval, orphan drug designation Binding: CH - Authorisation Type (required) #xD; Slices for coding 0..1 Coding Code defined by a terminology system Slice: Unordered, Open by value:system #xD; coding:CH 0..1 Coding Code defined by a terminology system #xD; system 1..1 uri Identity of the terminology system Required Pattern: http://fhir.ch/ig/ch-epl/CodeSystem/ch-authorisation-type #xD; code 1..1 code Symbol in syntax defined by the system #xD; region 0..* CodeableConcept The territory in which the authorization has been granted Required Pattern: At least the following #xD; coding 1..* Coding Code defined by a terminology system Fixed Value: (Complex) #xD; system 1..1 uri Identity of the terminology system Fixed Value: urn:iso:std:iso:3166 #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: CH #xD; status 0..1 CodeableConcept The status that is authorised e.g. approved. Intermediate states can be tracked with cases and applications Binding: CH SMC - Authorisation Status (required) #xD; Slices for coding 1..* Coding Code defined by a terminology system Slice: Unordered, Open by value:system #xD; coding:SMC 0..1 Coding Code defined by a terminology system #xD; system 1..1 uri Identity of the terminology system Required Pattern: http://fhir.ch/ig/ch-epl/CodeSystem/ch-SMC-authorisation-status #xD; code 1..1 code Symbol in syntax defined by the system #xD; coding:FOPH 0..1 Coding Code defined by a terminology system #xD; system 1..1 uri Identity of the terminology system Required Pattern: http://fhir.ch/ig/ch-epl/CodeSystem/ch-epl-foph-reimbursement-status #xD; code 1..1 code Symbol in syntax defined by the system #xD; holder 0..1 Reference(Organization) {c} The organization that has been granted this authorization, by the regulator #xD; regulator 0..1 Reference(Organization) {c} The regulatory authority or authorizing body granting the authorization #xD; <img src="[binary]" alt="doco" style="background-color: inherit"/> Documentation for this format
Profile of the RegulatedAuthorization resource for representing the market authorization of a (packaged) medicinal product.
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.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
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
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().ofType(canonical) | %resource.descendants().ofType(uri) | %resource.descendants().ofType(url))) or descendants().where(reference = '#').exists() or descendants().where(ofType(canonical) = '#').exists() or descendants().where(ofType(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
Marketing Authorization, Clinical Trial Authorization
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.
Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of its narrative along with other profiles, value sets, etc.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies its meaning or interpretation
The base language in which the resource is written.
Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).
Text summary of the resource, for human interpretation
A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.
Contained resources do not have a narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.
This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags in their meta elements, but SHALL NOT have security labels.
Additional content defined by implementations
May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and managable, 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.
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Must have either extensions or value[x], not both
May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it 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 managable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to 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).
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
Business identifier for the authorization, typically assigned by the authorizing body
Business identifier for the authorization, typically assigned by the authorizing body.
Marketing Authorization.Marketing Authorization Number
The product type, treatment, facility or activity that is being authorized
The product type, treatment, facility or activity that is being authorized.
(the link to Medicinal Product or Packaged Medicinal Product)
Overall type of this authorization, for example drug marketing approval, orphan drug designation
Overall type of this authorization, for example drug marketing approval, orphan drug designation.
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Extensions are always sliced by (at least) url
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 managable, 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.
A reference to a code defined by a terminology system.
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
Allows for alternative encodings within a code system, and translations to other code systems.
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
The identification of the code system that defines the meaning of the symbol in the code.
The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should be an absolute reference to some definition that establishes the system clearly and unambiguously.
Need to be unambiguous about the source of the definition of the symbol.
fhir:Coding.system rdfs:subPropertyOf dt:CDCoding.codeSystem
The version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured, and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged.
Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
fhir:Coding.version rdfs:subPropertyOf dt:CDCoding.codeSystemVersion
A symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination).
Need to refer to a particular code in the system.
fhir:Coding.code rdfs:subPropertyOf dt:CDCoding.code
A representation of the meaning of the code in the system, following the rules of the system.
Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
C*E.2 - but note this is not well followed
fhir:Coding.display rdfs:subPropertyOf dt:CDCoding.displayName
If this coding was chosen directly by the user
Indicates that this coding was chosen by a user directly - e.g. off a pick list of available items (codes or displays).
Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing.
fhir:Coding.userSelected fhir:mapsTo dt:CDCoding.codingRationale. fhir:Coding.userSelected fhir:hasMap fhir:Coding.userSelected.map. fhir:Coding.userSelected.map a fhir:Map; fhir:target dt:CDCoding.codingRationale. fhir:Coding.userSelected\#true a [ fhir:source "true"; fhir:target dt:CDCoding.codingRationale\#O ]
Plain text representation of the concept
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
Very often the text is the same as a displayName of one of the codings.
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
The territory in which the authorization has been granted
The territory (e.g., country, jurisdiction etc.) in which the authorization has been granted.
The status that is authorised e.g. approved. Intermediate states can be tracked with cases and applications
The status that is authorised e.g. approved. Intermediate states and actions can be tracked with cases and applications.
Marketing Authorization.Authorization Status
The date at which the current status was assigned
The date at which the current status was assigned.
Marketing Authorization.Authorization Status Date
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
The time period in which the regulatory approval, clearance or licencing is in effect. As an example, a Marketing Authorization includes the date of authorization and/or an expiration date.
Marketing Authorization.Validity Period Start, Marketing Authorization.Validity Period End
Condition for which the use of the regulated product applies
Condition for which the use of the regulated product applies.
The intended use of the product, e.g. prevention, treatment
The intended use of the product, e.g. prevention, treatment, diagnosis.
The legal/regulatory framework or reasons under which this authorization is granted
The legal or regulatory framework against which this authorization is granted, or other reasons for it.
A legal or regulatory framework against which an authorization is granted, or other reasons for it.
Marketing Authorization.Status Reasons.Legal Grounds
The organization that has been granted this authorization, by the regulator
The organization that has been granted this authorization, by some authoritative body (the 'regulator').
Marketing Authorization.Marketing Authorization Holder (Organisation)
The regulatory authority or authorizing body granting the authorization
The regulatory authority or authorizing body granting the authorization. For example, European Medicines Agency (EMA), Food and Drug Administration (FDA), Health Canada (HC), etc.
Marketing Authorization.Medicines Regulatory Agency (Organisation)
Additional information or supporting documentation about the authorization
Additional information or supporting documentation about the authorization.
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)
The case or regulatory procedure for granting or amending a regulated authorization. An authorization is granted in response to submissions/applications by those seeking authorization. A case is the administrative process that deals with the application(s) that relate to this and assesses them. Note: This area is subject to ongoing review and the workgroup is seeking implementer feedback on its use (see link at bottom of page).
Marketing Authorization.Marketing Authorization Procedure, Marketing Authorization Procedure.Marketing Authorization Application
Extensions that cannot be ignored even if unrecognized
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 managable, 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).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Identifier by which this case can be referenced
Identifier by which this case can be referenced.
Marketing Authorization Procedure.Procedure Identifier / Number, Marketing Authorization Application.Application Identifier / Number
The type of a case involved in an application.
Marketing Authorization Procedure.Procedure Type, Marketing Authorization Application.Application Type
Marketing Authorization Procedure.Procedure Date Start, Marketing Authorization Procedure.Procedure Date End, Marketing Authorization Application.Application Date
Applications submitted to obtain a regulated authorization. Steps within the longer running case or procedure
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.
Marketing Authorization.Marketing Authorization Application