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 ActivityDefinition Restrictions

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

Defines restrictive rules a ActivityDefinition 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
.. ActivityDefinition C 0..* ActivityDefinition The definition of a specific activity to be taken, independent of any particular patient or context
cnl-0: Name should be usable as an identifier for the module by machine processing applications such as code generation
... status ?!Σ 1..1 code draft | active | retired | unknown
Binding: PublicationStatus (required): The lifecycle status of an artifact.


ele-1: All FHIR elements must have a @value or children

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
ActivityDefinition.statusrequiredPublicationStatus
http://hl7.org/fhir/ValueSet/publication-status|5.0.0
from the FHIR Standard

This structure is derived from ActivityDefinition

NameFlagsCard.TypeDescription & Constraintsdoco
.. ActivityDefinition 0..* ActivityDefinition The definition of a specific activity to be taken, independent of any particular patient or context
... meta 0..0
... implicitRules 0..0
... language 0..0
... text 0..0
... contained 0..0
... modifierExtension 0..0
... url 0..0
... identifier 0..0
... version 0..0
... versionAlgorithm[x] 0..0
... name 0..0
... title 0..0
... subtitle 0..0
... experimental 0..0
... subject[x] 0..0
... date 0..0
... publisher 0..0
... contact 0..0
... description 0..0
... useContext 0..0
... jurisdiction 0..0
... purpose 0..0
... usage 0..0
... copyright 0..0
... copyrightLabel 0..0
... approvalDate 0..0
... lastReviewDate 0..0
... topic 0..0
... author 0..0
... editor 0..0
... reviewer 0..0
... endorser 0..0
... relatedArtifact 0..0
... library 0..0
... kind 0..0
... profile 0..0
... intent 0..0
... priority 0..0
... doNotPerform 0..0
... timing[x] 0..0
... asNeeded[x] 0..0
... location 0..0
... product[x] 0..0
... quantity 0..0
... dosage 0..0
... bodySite 0..0
... specimenRequirement 0..0
... observationRequirement 0..0
... observationResultRequirement 0..0
... transform 0..0
... dynamicValue 0..0

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. ActivityDefinition C 0..* ActivityDefinition The definition of a specific activity to be taken, independent of any particular patient or context
cnl-0: Name should be usable as an identifier for the module by machine processing applications such as code generation
... id Σ 0..1 id Logical id of this artifact
... extension 0..* Extension Additional content defined by implementations
... status ?!Σ 1..1 code draft | active | retired | unknown
Binding: PublicationStatus (required): The lifecycle status of an artifact.

... code Σ 0..1 CodeableConcept Detail type of activity
Binding: ProcedureCodesSNOMEDCT (example): Detailed type of the activity; e.g. CBC.

... participant 0..* BackboneElement Who should participate in the action
.... 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
.... type 0..1 code careteam | device | group | healthcareservice | location | organization | patient | practitioner | practitionerrole | relatedperson
Binding: ActionParticipantType (required): The type of participant in the activity.

.... typeCanonical 0..1 canonical(CapabilityStatement) Who or what can participate
.... typeReference 0..1 Reference(CareTeam | Device | DeviceDefinition | Endpoint | Group | HealthcareService | Location | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) Who or what can participate
.... role 0..1 CodeableConcept E.g. Nurse, Surgeon, Parent, etc
Binding: Action Participant Role (example): Defines roles played by participants for the action.

.... function 0..1 CodeableConcept E.g. Author, Reviewer, Witness, etc
Binding: ActionParticipantFunction (example)

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
ActivityDefinition.statusrequiredPublicationStatus
http://hl7.org/fhir/ValueSet/publication-status|5.0.0
from the FHIR Standard
ActivityDefinition.codeexampleProcedureCodesSNOMEDCT
http://hl7.org/fhir/ValueSet/procedure-code
from the FHIR Standard
ActivityDefinition.participant.typerequiredActionParticipantType
http://hl7.org/fhir/ValueSet/action-participant-type|5.0.0
from the FHIR Standard
ActivityDefinition.participant.roleexampleActionParticipantRole
http://terminology.hl7.org/ValueSet/action-participant-role
ActivityDefinition.participant.functionexampleActionParticipantFunction
http://hl7.org/fhir/ValueSet/action-participant-function
from the FHIR Standard

This structure is derived from ActivityDefinition

Summary

Prohibited: 51 elements

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. ActivityDefinition C 0..* ActivityDefinition The definition of a specific activity to be taken, independent of any particular patient or context
cnl-0: Name should be usable as an identifier for the module by machine processing applications such as code generation
... status ?!Σ 1..1 code draft | active | retired | unknown
Binding: PublicationStatus (required): The lifecycle status of an artifact.


ele-1: All FHIR elements must have a @value or children

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
ActivityDefinition.statusrequiredPublicationStatus
http://hl7.org/fhir/ValueSet/publication-status|5.0.0
from the FHIR Standard

Differential View

This structure is derived from ActivityDefinition

NameFlagsCard.TypeDescription & Constraintsdoco
.. ActivityDefinition 0..* ActivityDefinition The definition of a specific activity to be taken, independent of any particular patient or context
... meta 0..0
... implicitRules 0..0
... language 0..0
... text 0..0
... contained 0..0
... modifierExtension 0..0
... url 0..0
... identifier 0..0
... version 0..0
... versionAlgorithm[x] 0..0
... name 0..0
... title 0..0
... subtitle 0..0
... experimental 0..0
... subject[x] 0..0
... date 0..0
... publisher 0..0
... contact 0..0
... description 0..0
... useContext 0..0
... jurisdiction 0..0
... purpose 0..0
... usage 0..0
... copyright 0..0
... copyrightLabel 0..0
... approvalDate 0..0
... lastReviewDate 0..0
... topic 0..0
... author 0..0
... editor 0..0
... reviewer 0..0
... endorser 0..0
... relatedArtifact 0..0
... library 0..0
... kind 0..0
... profile 0..0
... intent 0..0
... priority 0..0
... doNotPerform 0..0
... timing[x] 0..0
... asNeeded[x] 0..0
... location 0..0
... product[x] 0..0
... quantity 0..0
... dosage 0..0
... bodySite 0..0
... specimenRequirement 0..0
... observationRequirement 0..0
... observationResultRequirement 0..0
... transform 0..0
... dynamicValue 0..0

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. ActivityDefinition C 0..* ActivityDefinition The definition of a specific activity to be taken, independent of any particular patient or context
cnl-0: Name should be usable as an identifier for the module by machine processing applications such as code generation
... id Σ 0..1 id Logical id of this artifact
... extension 0..* Extension Additional content defined by implementations
... status ?!Σ 1..1 code draft | active | retired | unknown
Binding: PublicationStatus (required): The lifecycle status of an artifact.

... code Σ 0..1 CodeableConcept Detail type of activity
Binding: ProcedureCodesSNOMEDCT (example): Detailed type of the activity; e.g. CBC.

... participant 0..* BackboneElement Who should participate in the action
.... 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
.... type 0..1 code careteam | device | group | healthcareservice | location | organization | patient | practitioner | practitionerrole | relatedperson
Binding: ActionParticipantType (required): The type of participant in the activity.

.... typeCanonical 0..1 canonical(CapabilityStatement) Who or what can participate
.... typeReference 0..1 Reference(CareTeam | Device | DeviceDefinition | Endpoint | Group | HealthcareService | Location | Organization | Patient | Practitioner | PractitionerRole | RelatedPerson) Who or what can participate
.... role 0..1 CodeableConcept E.g. Nurse, Surgeon, Parent, etc
Binding: Action Participant Role (example): Defines roles played by participants for the action.

.... function 0..1 CodeableConcept E.g. Author, Reviewer, Witness, etc
Binding: ActionParticipantFunction (example)

doco Documentation for this format

Terminology Bindings

PathConformanceValueSetURI
ActivityDefinition.statusrequiredPublicationStatus
http://hl7.org/fhir/ValueSet/publication-status|5.0.0
from the FHIR Standard
ActivityDefinition.codeexampleProcedureCodesSNOMEDCT
http://hl7.org/fhir/ValueSet/procedure-code
from the FHIR Standard
ActivityDefinition.participant.typerequiredActionParticipantType
http://hl7.org/fhir/ValueSet/action-participant-type|5.0.0
from the FHIR Standard
ActivityDefinition.participant.roleexampleActionParticipantRole
http://terminology.hl7.org/ValueSet/action-participant-role
ActivityDefinition.participant.functionexampleActionParticipantFunction
http://hl7.org/fhir/ValueSet/action-participant-function
from the FHIR Standard

This structure is derived from ActivityDefinition

Summary

Prohibited: 51 elements

 

Other representations of profile: CSV, Excel, Schematron