Connectathon 11 Snapshot

This page is part of the FHIR Specification (v1.2.0: STU 3 Draft). The current version which supercedes this version is 5.0.0. For a full list of available versions, see the Directory of published versions

U.S. Data Access Framework (DAF) Procedure Profile vs QICore-Procedure

Messages

A series of messages from the comparison algorithm. Errors indicate that solutions cannot be interoperable across both implementation guides (or that there are structural flaws in the definition of at least one).

PathMessage
Errors Detected
(None)
Notes about differences (e.g. definitions)
Procedure.extensionElements differ in definition for short:
"Additional Content defined by implementations"
"Extension"
Procedure.extensionElements differ in definition for definition:
"May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, 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."
"An Extension"
Procedure.codeElements differ in definition for short:
"SNOMED-CT | ICD-10 | CPT-4"
"Identification of the procedure"
Procedure.codeElements differ in definition for definition:
"SNOMED-CT | ICD-10 | CPT-4."
"The specific procedure that is performed. Use text if the exact nature of the procedure cannot be coded (e.g. "Laparoscopic Appendectomy")."

Intersection

The intersection of the 2 constraint statements. This is what resource authors (either client or server) would need to conform to produce content valid against both implementation guides.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Procedure I0..*ProcedureAn action that is being or was performed on a patient
pro-1: Reason not performed is only permitted if notPerformed indicator is true
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S ∑1..*IdentifierExternal Identifiers for this procedure
... subject S ∑1..1Reference(DAF-Patient)Who the procedure was performed on
... status ?! S∑1..1codein-progress | aborted | completed | entered-in-error
Binding: ProcedureStatus (required)
... category ∑0..1CodeableConceptClassification of the procedure
Binding: Procedure Category Codes (SNOMED CT) (example)
... code S ∑1..1CodeableConceptleft: SNOMED-CT | ICD-10 | CPT-4; right: Identification of the procedure
Binding: DAFProcedureType (preferred)
... notPerformed ?!0..1booleanTrue if procedure was not performed as scheduled
... reasonNotPerformed 0..*CodeableConceptReason procedure was not performed
Binding: Procedure Not Performed Reason (SNOMED-CT) (example)
... bodySite S ∑0..*CodeableConceptTarget body sites
Binding: SNOMED CT Body Structures (example)
... reason[x] S ∑0..1Condition, Reference(Condition)Reason procedure performed
Binding: Procedure Reason Codes (example)
... performer S ∑0..*BackboneElementThe people who performed the procedure
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... actor S ∑0..1Reference(DAF-Pract)The reference to the practitioner
.... role ∑0..1CodeableConceptThe role the actor was in
Binding: Procedure Performer Role Codes (example)
... performed[x] S ∑0..1dateTime, PeriodDate/Period the procedure was performed
... encounter S ∑0..1Reference(DAF-Encounter)The encounter associated with the procedure
... location ∑0..1Reference(QICore-Location)Where the procedure happened
... outcome ∑0..1CodeableConceptThe result of procedure
Binding: Procedure Outcome Codes (SNOMED CT) (example)
... report S0..*Reference(QICore-DiagnosticReport)Any report resulting from the procedure
... complication 0..*CodeableConceptComplication following the procedure
Binding: Condition/Problem/Diagnosis Codes (example)
... followUp 0..*CodeableConceptInstructions for follow up
Binding: Procedure Follow up Codes (SNOMED CT) (example)
... request 0..1Reference(CarePlan | DiagnosticOrder | ProcedureRequest | ReferralRequest)A request for this procedure
... notes 0..*AnnotationAdditional information about the procedure
... focalDevice 0..*BackboneElementDevice changed in procedure
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... action 0..1CodeableConceptKind of change to device
Binding: Procedure Device Action Codes (required)
.... manipulated 1..1Reference(QICore-Device)Device that was changed
... used 0..*Reference(Device | Medication | Substance)Items used during procedure

doco Documentation for this format

Union

The union of the 2 constraint statements. This is what resource authors (either client or server) would need to be able to handle to accept content valid against either implementation guides.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Procedure I0..*ProcedureAn action that is being or was performed on a patient
pro-1: Reason not performed is only permitted if notPerformed indicator is true
... meta ∑0..1MetaMetadata about the resource
... implicitRules ?! ∑0..1uriA set of rules under which this content was created
... language 0..1codeLanguage of the resource content
Binding: IETF BCP-47 (required)
... text 0..1NarrativeText summary of the resource, for human interpretation
... contained 0..*ResourceContained, inline Resources
... procedure-approachBodySite 0..*Reference(BodySite)Extension
URL: http://hl7.org/fhir/StructureDefinition/procedure-approachBodySite
... procedure-incisionDateTime 0..1dateTimeExtension
URL: http://hl7.org/fhir/StructureDefinition/procedure-incisionDateTime
... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
... identifier S ∑0..*IdentifierExternal Identifiers for this procedure
... subject S ∑1..1Reference(#1 | Group)Who the procedure was performed on
... status ?! S∑1..1codein-progress | aborted | completed | entered-in-error
Binding: ProcedureStatus (required)
... category ∑0..1CodeableConceptClassification of the procedure
Binding: Procedure Category Codes (SNOMED CT) (example)
... code S ∑1..1CodeableConceptleft: SNOMED-CT | ICD-10 | CPT-4; right: Identification of the procedure
Binding: DAFProcedureType (preferred)
... notPerformed ?!0..1booleanTrue if procedure was not performed as scheduled
... reasonNotPerformed 0..*CodeableConceptReason procedure was not performed
Binding: Procedure Not Performed Reason (SNOMED-CT) (example)
... bodySite S ∑0..*CodeableConceptTarget body sites
Binding: SNOMED CT Body Structures (example)
... reason[x] S ∑0..1CodeableConcept, Reference(Condition)Reason procedure performed
Binding: Procedure Reason Codes (example)
... performer S ∑0..*BackboneElementThe people who performed the procedure
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... actor S ∑0..1Reference(#3 | QICore-Organization | QICore-Patient | QICore-RelatedPerson)The reference to the practitioner
.... role ∑0..1CodeableConceptThe role the actor was in
Binding: Procedure Performer Role Codes (example)
... performed[x] S ∑0..1dateTime, PeriodDate/Period the procedure was performed
... encounter S ∑0..1Reference(#4)The encounter associated with the procedure
... location ∑0..1Reference(Location)Where the procedure happened
... outcome ∑0..1CodeableConceptThe result of procedure
Binding: Procedure Outcome Codes (SNOMED CT) (example)
... report S0..*Reference(DiagnosticReport)Any report resulting from the procedure
... complication 0..*CodeableConceptComplication following the procedure
Binding: Condition/Problem/Diagnosis Codes (example)
... followUp 0..*CodeableConceptInstructions for follow up
Binding: Procedure Follow up Codes (SNOMED CT) (example)
... request 0..1Reference(CarePlan | DiagnosticOrder | ProcedureRequest | ReferralRequest)A request for this procedure
... notes 0..*AnnotationAdditional information about the procedure
... focalDevice 0..*BackboneElementDevice changed in procedure
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... action 0..1CodeableConceptKind of change to device
Binding: Procedure Device Action Codes (required)
.... manipulated 1..1Reference(Device)Device that was changed
... used 0..*Reference(Device | Medication | Substance)Items used during procedure

doco Documentation for this format