FHIR.SHINNY\US Core Procedure Profile

0.2 - ci-build

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

Resource Profile: US Core Procedure Profile

Official URL: http://shinny.org/StructureDefinition/us-core-procedure		Version: 0.2
Active as of 2022-04-20	Realm:	Computable Name: USCoreProcedureProfile
Copyright/Legal: Used by permission of HL7 International, all rights reserved Creative Commons License

The US Core Procedure Profile is based upon the core FHIR Procedure Resource and meets the U.S. Core Data for Interoperability (USCDI) v2 ‘Procedures’ requirements. This profile sets minimum expectations for the Procedure resource to record, search, and fetch procedures associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource when using this profile. It provides the floor for standards development for specific use cases.

Usage:

Derived from this Resource Profile: SHINNY Procedure Profile
Refer to this Resource Profile: US Core Encounter Profile

Formal Views of Profile Content

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

Differential Table
Key Elements Table
Snapshot Table
Statistics/References
All

This structure is derived from Procedure

Name	Flags	Card.	Type	Description & Constraints
Procedure	C	0..*	Procedure	An action that is being or was performed on a patient us-core-7: Performed SHALL be present if the status is 'completed' or 'in-progress'
basedOn		0..*	Reference(US Core CarePlan Profile \| US Core ServiceRequest Profile)	A request for this procedure
status	SC	1..1	code	preparation \| in-progress \| not-done \| on-hold \| stopped \| completed \| entered-in-error \| unknown Binding: EventStatus (required)
code	S	1..1	CodeableConcept	Identification of the procedure Binding: US Core Procedure Codes (preferred): Codes describing the type of Procedure
subject	S	1..1	Reference(US Core Patient Profile)	Who the procedure was performed on
performed[x]	SC	0..1		When the procedure was performed
performedDateTime			dateTime S
performedPeriod			Period
performedString			string
performedAge			Age
performedRange			Range
recorder		0..1	Reference(SHINNY Patient Profile \| RelatedPerson \| Practitioner \| PractitionerRole)	Who recorded the procedure
asserter		0..1	Reference(SHINNY Patient Profile \| RelatedPerson \| Practitioner \| PractitionerRole)	Person who asserts this procedure
Documentation for this format

Terminology Bindings (Differential)

Path	Conformance	ValueSet
Procedure.status	required	EventStatus
Procedure.code	preferred	USCoreProcedureCodes

Constraints

Id	Grade	Path(s)	Details	Requirements
us-core-7	error	Procedure	Performed SHALL be present if the status is 'completed' or 'in-progress' : (status='completed' or status='in-progress') implies performed.exists()

Name	Flags	Card.	Type	Description & Constraints
Procedure	C	0..*	Procedure	An action that is being or was performed on a patient us-core-7: Performed SHALL be present if the status is 'completed' or 'in-progress'
implicitRules	?!Σ	0..1	uri	A set of rules under which this content was created
modifierExtension	?!	0..*	Extension	Extensions that cannot be ignored
basedOn	Σ	0..*	Reference(US Core CarePlan Profile \| US Core ServiceRequest Profile)	A request for this procedure
status	?!SΣC	1..1	code	preparation \| in-progress \| not-done \| on-hold \| stopped \| completed \| entered-in-error \| unknown Binding: EventStatus (required)
code	SΣ	1..1	CodeableConcept	Identification of the procedure Binding: US Core Procedure Codes (preferred): Codes describing the type of Procedure
subject	SΣ	1..1	Reference(US Core Patient Profile)	Who the procedure was performed on
performed[x]	SΣC	0..1		When the procedure was performed
performedDateTime			dateTime
recorder	Σ	0..1	Reference(SHINNY Patient Profile \| RelatedPerson \| Practitioner \| PractitionerRole)	Who recorded the procedure
asserter	Σ	0..1	Reference(SHINNY Patient Profile \| RelatedPerson \| Practitioner \| PractitionerRole)	Person who asserts this procedure
Documentation for this format

Terminology Bindings

Path	Conformance	ValueSet
Procedure.status	required	EventStatus
Procedure.code	preferred	USCoreProcedureCodes

Constraints

Id	Grade	Path(s)	Details	Requirements
dom-2	error	Procedure	If the resource is contained in another resource, it SHALL NOT contain nested Resources : contained.contained.empty()
dom-3	error	Procedure	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().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-4	error	Procedure	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()
dom-5	error	Procedure	If a resource is contained in another resource, it SHALL NOT have a security label : contained.meta.security.empty()
dom-6	best practice	Procedure	A resource should have narrative for robust management : text.`div`.exists()
ele-1	error	ALL elements	All FHIR elements must have a @value or children : hasValue() or (children().count() > id.count())
ext-1	error	ALL extensions	Must have either extensions or value[x], not both : extension.exists() != value.exists()
us-core-7	error	Procedure	Performed SHALL be present if the status is 'completed' or 'in-progress' : (status='completed' or status='in-progress') implies performed.exists()