0.2 - ci-build

SHINNYIG - Local Development build (v0.2). See the Directory of published versions

Resource Profile: SHINNY Procedure Profile

Official URL: http://shinny.org/StructureDefinition/shin-ny-procedure Version: 0.2
Active as of 2023-07-28 Computable Name: SHINNYProcedureProfile

An action that is being or was performed on a patient

Usage:

Formal Views of Profile Content

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

This structure is derived from USCoreProcedureProfile

NameFlagsCard.TypeDescription & Constraintsdoco
.. Procedure 0..*USCoreProcedureProfileAn action that is being or was performed on a patient
... id S1..1idThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
... meta S1..1SHINNYMetaMetadata about a resource
... language S0..1codeLanguage of the resource content
... subject 1..1Reference(SHINNY Patient Profile)Who the procedure was performed on
... encounter 0..1Reference(SHINNY Encounter Profile)Encounter created as part of
... performer S0..*BackboneElementThe people who performed the procedure
.... actor 1..1Reference(US Core Practitioner Profile | US Core PractitionerRole Profile)The reference to the practitioner
... location S0..1Reference(Location)Where the procedure happened
... reasonCode S0..*CodeableConceptCoded reason procedure performed
... reasonReference S0..*Reference(SHINNY Diagnosis Profile | SHINNY Procedure Profile | SHINNY Observation Profile)The justification that the procedure was performed
... bodySite S0..*CodeableConceptTarget body sites
... outcome S0..1CodeableConceptThe result of procedure
... complication S0..*CodeableConceptComplication following the procedure
... complicationDetail S0..*Reference(SHINNY Diagnosis Profile)A condition that is a result of the procedure

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. Procedure C0..*USCoreProcedureProfileAn action that is being or was performed on a patient
... id SΣ1..1idThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
... meta S1..1SHINNYMetaMetadata about a resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... partOf SΣ0..*Reference(SHINNY Procedure Profile | SHINNY Observation Profile)Part of referenced event
... status ?!SΣC1..1codepreparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
Binding: EventStatus (required)
... code SΣ1..1CodeableConceptIdentification of the procedure
Binding: US Core Procedure Codes (preferred): Codes describing the type of Procedure

... subject SΣ1..1Reference(SHINNY Patient Profile)Who the procedure was performed on
... encounter Σ0..1Reference(SHINNY Encounter Profile)Encounter created as part of
... performed[x] SΣC0..1When the procedure was performed
.... performedDateTimedateTime
... performer SΣ0..*BackboneElementThe people who performed the procedure
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... actor Σ1..1Reference(US Core Practitioner Profile | US Core PractitionerRole Profile)The reference to the practitioner
... location SΣ0..1Reference(Location)Where the procedure happened
... reasonCode SΣ0..*CodeableConceptCoded reason procedure performed
Binding: ProcedureReasonCodes (example): A code that identifies the reason a procedure is required.


... reasonReference SΣ0..*Reference(SHINNY Diagnosis Profile | SHINNY Procedure Profile | SHINNY Observation Profile)The justification that the procedure was performed
... bodySite SΣ0..*CodeableConceptTarget body sites
Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.


... outcome SΣ0..1CodeableConceptThe result of procedure
Binding: ProcedureOutcomeCodes(SNOMEDCT) (example): An outcome of a procedure - whether it was resolved or otherwise.

... complication S0..*CodeableConceptComplication following the procedure
Binding: Condition/Problem/DiagnosisCodes (example): Codes describing complications that resulted from a procedure.


... complicationDetail S0..*Reference(SHINNY Diagnosis Profile)A condition that is a result of the procedure

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
Procedure.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
Procedure.statusrequiredEventStatus
Procedure.codepreferredUSCoreProcedureCodes
Procedure.reasonCodeexampleProcedureReasonCodes
Procedure.bodySiteexampleSNOMEDCTBodyStructures
Procedure.outcomeexampleProcedureOutcomeCodes(SNOMEDCT)
Procedure.complicationexampleCondition/Problem/DiagnosisCodes

Constraints

IdGradePath(s)DetailsRequirements
dom-2errorProcedureIf the resource is contained in another resource, it SHALL NOT contain nested Resources
: contained.contained.empty()
dom-3errorProcedureIf 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().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4errorProcedureIf 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()
dom-5errorProcedureIf a resource is contained in another resource, it SHALL NOT have a security label
: contained.meta.security.empty()
dom-6best practiceProcedureA resource should have narrative for robust management
: text.`div`.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()
us-core-7errorProcedurePerformed SHALL be present if the status is 'completed' or 'in-progress'
: (status='completed' or status='in-progress') implies performed.exists()
NameFlagsCard.TypeDescription & Constraintsdoco
.. Procedure C0..*USCoreProcedureProfileAn action that is being or was performed on a patient
... id SΣ1..1idThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
... meta S1..1SHINNYMetaMetadata about a resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language S0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierExternal Identifiers for this procedure
... instantiatesCanonical Σ0..*canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire)Instantiates FHIR protocol or definition
... instantiatesUri Σ0..*uriInstantiates external protocol or definition
... basedOn Σ0..*Reference(US Core CarePlan Profile | US Core ServiceRequest Profile)A request for this procedure
... partOf SΣ0..*Reference(SHINNY Procedure Profile | SHINNY Observation Profile)Part of referenced event
... status ?!SΣC1..1codepreparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
Binding: EventStatus (required)
... statusReason Σ0..1CodeableConceptReason for current status
Binding: ProcedureNotPerformedReason(SNOMED-CT) (example): A code that identifies the reason a procedure was not performed.

... category Σ0..1CodeableConceptClassification of the procedure
Binding: ProcedureCategoryCodes(SNOMEDCT) (example): A code that classifies a procedure for searching, sorting and display purposes.

... code SΣ1..1CodeableConceptIdentification of the procedure
Binding: US Core Procedure Codes (preferred): Codes describing the type of Procedure

... subject SΣ1..1Reference(SHINNY Patient Profile)Who the procedure was performed on
... encounter Σ0..1Reference(SHINNY Encounter Profile)Encounter created as part of
... performed[x] SΣC0..1When the procedure was performed
.... performedDateTimedateTime S
.... performedPeriodPeriod
.... performedStringstring
.... performedAgeAge
.... performedRangeRange
... recorder Σ0..1Reference(SHINNY Patient Profile | RelatedPerson | Practitioner | PractitionerRole)Who recorded the procedure
... asserter Σ0..1Reference(SHINNY Patient Profile | RelatedPerson | Practitioner | PractitionerRole)Person who asserts this procedure
... performer SΣ0..*BackboneElementThe people who performed the procedure
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... function Σ0..1CodeableConceptType of performance
Binding: ProcedurePerformerRoleCodes (example): A code that identifies the role of a performer of the procedure.

.... actor Σ1..1Reference(US Core Practitioner Profile | US Core PractitionerRole Profile)The reference to the practitioner
.... onBehalfOf 0..1Reference(Organization)Organization the device or practitioner was acting for
... location SΣ0..1Reference(Location)Where the procedure happened
... reasonCode SΣ0..*CodeableConceptCoded reason procedure performed
Binding: ProcedureReasonCodes (example): A code that identifies the reason a procedure is required.


... reasonReference SΣ0..*Reference(SHINNY Diagnosis Profile | SHINNY Procedure Profile | SHINNY Observation Profile)The justification that the procedure was performed
... bodySite SΣ0..*CodeableConceptTarget body sites
Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.


... outcome SΣ0..1CodeableConceptThe result of procedure
Binding: ProcedureOutcomeCodes(SNOMEDCT) (example): An outcome of a procedure - whether it was resolved or otherwise.

... report 0..*Reference(DiagnosticReport | DocumentReference | Composition)Any report resulting from the procedure
... complication S0..*CodeableConceptComplication following the procedure
Binding: Condition/Problem/DiagnosisCodes (example): Codes describing complications that resulted from a procedure.


... complicationDetail S0..*Reference(SHINNY Diagnosis Profile)A condition that is a result of the procedure
... followUp 0..*CodeableConceptInstructions for follow up
Binding: ProcedureFollowUpCodes(SNOMEDCT) (example): Specific follow up required for a procedure e.g. removal of sutures.


... note 0..*AnnotationAdditional information about the procedure
... focalDevice 0..*BackboneElementManipulated, implanted, or removed device
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... action 0..1CodeableConceptKind of change to device
Binding: ProcedureDeviceActionCodes (preferred): A kind of change that happened to the device during the procedure.

.... manipulated 1..1Reference(Device)Device that was changed
... usedReference 0..*Reference(Device | Medication | Substance)Items used during procedure
... usedCode 0..*CodeableConceptCoded items used during the procedure
Binding: FHIRDeviceTypes (example): Codes describing items used during a procedure.



doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
Procedure.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
Procedure.statusrequiredEventStatus
Procedure.statusReasonexampleProcedureNotPerformedReason(SNOMED-CT)
Procedure.categoryexampleProcedureCategoryCodes(SNOMEDCT)
Procedure.codepreferredUSCoreProcedureCodes
Procedure.performer.functionexampleProcedurePerformerRoleCodes
Procedure.reasonCodeexampleProcedureReasonCodes
Procedure.bodySiteexampleSNOMEDCTBodyStructures
Procedure.outcomeexampleProcedureOutcomeCodes(SNOMEDCT)
Procedure.complicationexampleCondition/Problem/DiagnosisCodes
Procedure.followUpexampleProcedureFollowUpCodes(SNOMEDCT)
Procedure.focalDevice.actionpreferredProcedureDeviceActionCodes
Procedure.usedCodeexampleFHIRDeviceTypes

Constraints

IdGradePath(s)DetailsRequirements
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()

Differential View

This structure is derived from USCoreProcedureProfile

NameFlagsCard.TypeDescription & Constraintsdoco
.. Procedure 0..*USCoreProcedureProfileAn action that is being or was performed on a patient
... id S1..1idThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
... meta S1..1SHINNYMetaMetadata about a resource
... language S0..1codeLanguage of the resource content
... subject 1..1Reference(SHINNY Patient Profile)Who the procedure was performed on
... encounter 0..1Reference(SHINNY Encounter Profile)Encounter created as part of
... performer S0..*BackboneElementThe people who performed the procedure
.... actor 1..1Reference(US Core Practitioner Profile | US Core PractitionerRole Profile)The reference to the practitioner
... location S0..1Reference(Location)Where the procedure happened
... reasonCode S0..*CodeableConceptCoded reason procedure performed
... reasonReference S0..*Reference(SHINNY Diagnosis Profile | SHINNY Procedure Profile | SHINNY Observation Profile)The justification that the procedure was performed
... bodySite S0..*CodeableConceptTarget body sites
... outcome S0..1CodeableConceptThe result of procedure
... complication S0..*CodeableConceptComplication following the procedure
... complicationDetail S0..*Reference(SHINNY Diagnosis Profile)A condition that is a result of the procedure

doco Documentation for this format

Key Elements View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Procedure C0..*USCoreProcedureProfileAn action that is being or was performed on a patient
... id SΣ1..1idThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
... meta S1..1SHINNYMetaMetadata about a resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... partOf SΣ0..*Reference(SHINNY Procedure Profile | SHINNY Observation Profile)Part of referenced event
... status ?!SΣC1..1codepreparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
Binding: EventStatus (required)
... code SΣ1..1CodeableConceptIdentification of the procedure
Binding: US Core Procedure Codes (preferred): Codes describing the type of Procedure

... subject SΣ1..1Reference(SHINNY Patient Profile)Who the procedure was performed on
... encounter Σ0..1Reference(SHINNY Encounter Profile)Encounter created as part of
... performed[x] SΣC0..1When the procedure was performed
.... performedDateTimedateTime
... performer SΣ0..*BackboneElementThe people who performed the procedure
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... actor Σ1..1Reference(US Core Practitioner Profile | US Core PractitionerRole Profile)The reference to the practitioner
... location SΣ0..1Reference(Location)Where the procedure happened
... reasonCode SΣ0..*CodeableConceptCoded reason procedure performed
Binding: ProcedureReasonCodes (example): A code that identifies the reason a procedure is required.


... reasonReference SΣ0..*Reference(SHINNY Diagnosis Profile | SHINNY Procedure Profile | SHINNY Observation Profile)The justification that the procedure was performed
... bodySite SΣ0..*CodeableConceptTarget body sites
Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.


... outcome SΣ0..1CodeableConceptThe result of procedure
Binding: ProcedureOutcomeCodes(SNOMEDCT) (example): An outcome of a procedure - whether it was resolved or otherwise.

... complication S0..*CodeableConceptComplication following the procedure
Binding: Condition/Problem/DiagnosisCodes (example): Codes describing complications that resulted from a procedure.


... complicationDetail S0..*Reference(SHINNY Diagnosis Profile)A condition that is a result of the procedure

doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
Procedure.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
Procedure.statusrequiredEventStatus
Procedure.codepreferredUSCoreProcedureCodes
Procedure.reasonCodeexampleProcedureReasonCodes
Procedure.bodySiteexampleSNOMEDCTBodyStructures
Procedure.outcomeexampleProcedureOutcomeCodes(SNOMEDCT)
Procedure.complicationexampleCondition/Problem/DiagnosisCodes

Constraints

IdGradePath(s)DetailsRequirements
dom-2errorProcedureIf the resource is contained in another resource, it SHALL NOT contain nested Resources
: contained.contained.empty()
dom-3errorProcedureIf 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().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4errorProcedureIf 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()
dom-5errorProcedureIf a resource is contained in another resource, it SHALL NOT have a security label
: contained.meta.security.empty()
dom-6best practiceProcedureA resource should have narrative for robust management
: text.`div`.exists()
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()
us-core-7errorProcedurePerformed SHALL be present if the status is 'completed' or 'in-progress'
: (status='completed' or status='in-progress') implies performed.exists()

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Procedure C0..*USCoreProcedureProfileAn action that is being or was performed on a patient
... id SΣ1..1idThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
... meta S1..1SHINNYMetaMetadata about a resource
... implicitRules ?!Σ0..1uriA set of rules under which this content was created
... language S0..1codeLanguage of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional BindingsPurpose
AllLanguagesMax Binding
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... extension 0..*ExtensionAdditional content defined by implementations
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier Σ0..*IdentifierExternal Identifiers for this procedure
... instantiatesCanonical Σ0..*canonical(PlanDefinition | ActivityDefinition | Measure | OperationDefinition | Questionnaire)Instantiates FHIR protocol or definition
... instantiatesUri Σ0..*uriInstantiates external protocol or definition
... basedOn Σ0..*Reference(US Core CarePlan Profile | US Core ServiceRequest Profile)A request for this procedure
... partOf SΣ0..*Reference(SHINNY Procedure Profile | SHINNY Observation Profile)Part of referenced event
... status ?!SΣC1..1codepreparation | in-progress | not-done | on-hold | stopped | completed | entered-in-error | unknown
Binding: EventStatus (required)
... statusReason Σ0..1CodeableConceptReason for current status
Binding: ProcedureNotPerformedReason(SNOMED-CT) (example): A code that identifies the reason a procedure was not performed.

... category Σ0..1CodeableConceptClassification of the procedure
Binding: ProcedureCategoryCodes(SNOMEDCT) (example): A code that classifies a procedure for searching, sorting and display purposes.

... code SΣ1..1CodeableConceptIdentification of the procedure
Binding: US Core Procedure Codes (preferred): Codes describing the type of Procedure

... subject SΣ1..1Reference(SHINNY Patient Profile)Who the procedure was performed on
... encounter Σ0..1Reference(SHINNY Encounter Profile)Encounter created as part of
... performed[x] SΣC0..1When the procedure was performed
.... performedDateTimedateTime S
.... performedPeriodPeriod
.... performedStringstring
.... performedAgeAge
.... performedRangeRange
... recorder Σ0..1Reference(SHINNY Patient Profile | RelatedPerson | Practitioner | PractitionerRole)Who recorded the procedure
... asserter Σ0..1Reference(SHINNY Patient Profile | RelatedPerson | Practitioner | PractitionerRole)Person who asserts this procedure
... performer SΣ0..*BackboneElementThe people who performed the procedure
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... function Σ0..1CodeableConceptType of performance
Binding: ProcedurePerformerRoleCodes (example): A code that identifies the role of a performer of the procedure.

.... actor Σ1..1Reference(US Core Practitioner Profile | US Core PractitionerRole Profile)The reference to the practitioner
.... onBehalfOf 0..1Reference(Organization)Organization the device or practitioner was acting for
... location SΣ0..1Reference(Location)Where the procedure happened
... reasonCode SΣ0..*CodeableConceptCoded reason procedure performed
Binding: ProcedureReasonCodes (example): A code that identifies the reason a procedure is required.


... reasonReference SΣ0..*Reference(SHINNY Diagnosis Profile | SHINNY Procedure Profile | SHINNY Observation Profile)The justification that the procedure was performed
... bodySite SΣ0..*CodeableConceptTarget body sites
Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.


... outcome SΣ0..1CodeableConceptThe result of procedure
Binding: ProcedureOutcomeCodes(SNOMEDCT) (example): An outcome of a procedure - whether it was resolved or otherwise.

... report 0..*Reference(DiagnosticReport | DocumentReference | Composition)Any report resulting from the procedure
... complication S0..*CodeableConceptComplication following the procedure
Binding: Condition/Problem/DiagnosisCodes (example): Codes describing complications that resulted from a procedure.


... complicationDetail S0..*Reference(SHINNY Diagnosis Profile)A condition that is a result of the procedure
... followUp 0..*CodeableConceptInstructions for follow up
Binding: ProcedureFollowUpCodes(SNOMEDCT) (example): Specific follow up required for a procedure e.g. removal of sutures.


... note 0..*AnnotationAdditional information about the procedure
... focalDevice 0..*BackboneElementManipulated, implanted, or removed device
.... id 0..1stringUnique id for inter-element referencing
.... extension 0..*ExtensionAdditional content defined by implementations
.... modifierExtension ?!Σ0..*ExtensionExtensions that cannot be ignored even if unrecognized
.... action 0..1CodeableConceptKind of change to device
Binding: ProcedureDeviceActionCodes (preferred): A kind of change that happened to the device during the procedure.

.... manipulated 1..1Reference(Device)Device that was changed
... usedReference 0..*Reference(Device | Medication | Substance)Items used during procedure
... usedCode 0..*CodeableConceptCoded items used during the procedure
Binding: FHIRDeviceTypes (example): Codes describing items used during a procedure.



doco Documentation for this format

Terminology Bindings

PathConformanceValueSet
Procedure.languagepreferredCommonLanguages
Additional Bindings Purpose
AllLanguages Max Binding
Procedure.statusrequiredEventStatus
Procedure.statusReasonexampleProcedureNotPerformedReason(SNOMED-CT)
Procedure.categoryexampleProcedureCategoryCodes(SNOMEDCT)
Procedure.codepreferredUSCoreProcedureCodes
Procedure.performer.functionexampleProcedurePerformerRoleCodes
Procedure.reasonCodeexampleProcedureReasonCodes
Procedure.bodySiteexampleSNOMEDCTBodyStructures
Procedure.outcomeexampleProcedureOutcomeCodes(SNOMEDCT)
Procedure.complicationexampleCondition/Problem/DiagnosisCodes
Procedure.followUpexampleProcedureFollowUpCodes(SNOMEDCT)
Procedure.focalDevice.actionpreferredProcedureDeviceActionCodes
Procedure.usedCodeexampleFHIRDeviceTypes

Constraints

IdGradePath(s)DetailsRequirements
ele-1error**ALL** elementsAll FHIR elements must have a @value or children
: hasValue() or (children().count() > id.count())
ext-1error**ALL** extensionsMust have either extensions or value[x], not both
: extension.exists() != value.exists()

 

Other representations of profile: CSV, Excel, Schematron