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

K.9 StructureDefinition: GAO Diagnostic Order

The official URL for this profile is: 

http://hl7.org/fhir/StructureDefinition/gao-diagnosticorder

Profiles the diagnostic order to ensure that the services ordered can be identified and evaluated for appropraiteness

This profile was published on [no date] with unknown status '" by .

K.9.1 Formal Views of Profile Content

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

This structure is derived from DiagnosticOrder.

Summary

Mandatory: 1 element (+1 nested mandatory element)
Must-Support: 3 elements

This structure is derived from DiagnosticOrder.

NameFlagsCard.TypeDescription & Constraintsdoco
.. DiagnosticOrder 0..*DiagnosticOrderA request for a diagnostic service
... supportingInformation S0..*Reference(Observation | Condition | DocumentReference)Additional clinical information
... item 1..*BackboneElementThe items the orderer requested
.... bodySite S0..1CodeableConceptLocation of requested test (if applicable)
Binding: SNOMED CT Body Structures (example)
... note S0..*AnnotationOther notes and comments

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraintsdoco
.. DiagnosticOrder 0..*DiagnosticOrderA request for a diagnostic service
... 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 I0..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
... subject ∑1..1Reference(Patient | Group | Location | Device)Who and/or what test is about
... orderer ∑0..1Reference(Practitioner)Who ordered the test
... identifier ∑0..*IdentifierIdentifiers assigned to this order
... encounter ∑0..1Reference(Encounter)The encounter that this diagnostic order is associated with
... reason 0..*CodeableConceptExplanation/Justification for test
Binding: Condition/Problem/Diagnosis Codes (example)
... supportingInformation S0..*Reference(Observation | Condition | DocumentReference)Additional clinical information
... specimen 0..*Reference(Specimen)If the whole order relates to specific specimens
... status ?! ∑0..1codeproposed | draft | planned | requested | received | accepted | in-progress | review | completed | cancelled | suspended | rejected | failed
Binding: DiagnosticOrderStatus (required)
... priority ∑0..1coderoutine | urgent | stat | asap
Binding: DiagnosticOrderPriority (required)
... event 0..*BackboneElementA list of events of interest in the lifecycle
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... status ∑1..1codeproposed | draft | planned | requested | received | accepted | in-progress | review | completed | cancelled | suspended | rejected | failed
Binding: DiagnosticOrderStatus (required)
.... description ∑0..1CodeableConceptMore information about the event and its context
Binding: Diagnostic Order Event Codes (example)
.... dateTime ∑1..1dateTimeThe date at which the event happened
.... actor 0..1Reference(Practitioner | Device)Who recorded or did this
... item 1..*BackboneElementThe items the orderer requested
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... code ∑1..1CodeableConceptCode to indicate the item (test or panel) being ordered
Binding: LOINC Diagnostic Order Codes (preferred)
.... specimen 0..*Reference(Specimen)If this item relates to specific specimens
.... bodySite S0..1CodeableConceptLocation of requested test (if applicable)
Binding: SNOMED CT Body Structures (example)
.... status ∑0..1codeproposed | draft | planned | requested | received | accepted | in-progress | review | completed | cancelled | suspended | rejected | failed
Binding: DiagnosticOrderStatus (required)
.... event ∑0..*See DiagnosticOrder.eventEvents specific to this item
... note S0..*AnnotationOther notes and comments

doco Documentation for this format

todo

This structure is derived from DiagnosticOrder.

Summary

Mandatory: 1 element (+1 nested mandatory element)
Must-Support: 3 elements

Differential View

This structure is derived from DiagnosticOrder.

NameFlagsCard.TypeDescription & Constraintsdoco
.. DiagnosticOrder 0..*DiagnosticOrderA request for a diagnostic service
... supportingInformation S0..*Reference(Observation | Condition | DocumentReference)Additional clinical information
... item 1..*BackboneElementThe items the orderer requested
.... bodySite S0..1CodeableConceptLocation of requested test (if applicable)
Binding: SNOMED CT Body Structures (example)
... note S0..*AnnotationOther notes and comments

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. DiagnosticOrder 0..*DiagnosticOrderA request for a diagnostic service
... 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 I0..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
... subject ∑1..1Reference(Patient | Group | Location | Device)Who and/or what test is about
... orderer ∑0..1Reference(Practitioner)Who ordered the test
... identifier ∑0..*IdentifierIdentifiers assigned to this order
... encounter ∑0..1Reference(Encounter)The encounter that this diagnostic order is associated with
... reason 0..*CodeableConceptExplanation/Justification for test
Binding: Condition/Problem/Diagnosis Codes (example)
... supportingInformation S0..*Reference(Observation | Condition | DocumentReference)Additional clinical information
... specimen 0..*Reference(Specimen)If the whole order relates to specific specimens
... status ?! ∑0..1codeproposed | draft | planned | requested | received | accepted | in-progress | review | completed | cancelled | suspended | rejected | failed
Binding: DiagnosticOrderStatus (required)
... priority ∑0..1coderoutine | urgent | stat | asap
Binding: DiagnosticOrderPriority (required)
... event 0..*BackboneElementA list of events of interest in the lifecycle
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... status ∑1..1codeproposed | draft | planned | requested | received | accepted | in-progress | review | completed | cancelled | suspended | rejected | failed
Binding: DiagnosticOrderStatus (required)
.... description ∑0..1CodeableConceptMore information about the event and its context
Binding: Diagnostic Order Event Codes (example)
.... dateTime ∑1..1dateTimeThe date at which the event happened
.... actor 0..1Reference(Practitioner | Device)Who recorded or did this
... item 1..*BackboneElementThe items the orderer requested
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... code ∑1..1CodeableConceptCode to indicate the item (test or panel) being ordered
Binding: LOINC Diagnostic Order Codes (preferred)
.... specimen 0..*Reference(Specimen)If this item relates to specific specimens
.... bodySite S0..1CodeableConceptLocation of requested test (if applicable)
Binding: SNOMED CT Body Structures (example)
.... status ∑0..1codeproposed | draft | planned | requested | received | accepted | in-progress | review | completed | cancelled | suspended | rejected | failed
Binding: DiagnosticOrderStatus (required)
.... event ∑0..*See DiagnosticOrder.eventEvents specific to this item
... note S0..*AnnotationOther notes and comments

doco Documentation for this format

XML Template

JSON Template

todo

 

Other representations of profile: Schematron

K.9.2 Terminology Bindings

PathNameConformanceValueSet
DiagnosticOrder.language?extrequiredhttp://tools.ietf.org/html/bcp47
DiagnosticOrder.reasonCondition/Problem/Diagnosis CodesexampleCondition/Problem/Diagnosis Codes
DiagnosticOrder.statusDiagnosticOrderStatusrequiredDiagnosticOrderStatus
DiagnosticOrder.priorityDiagnosticOrderPriorityrequiredDiagnosticOrderPriority
DiagnosticOrder.event.statusDiagnosticOrderStatusrequiredDiagnosticOrderStatus
DiagnosticOrder.event.descriptionDiagnostic Order Event CodesexampleDiagnostic Order Event Codes
DiagnosticOrder.item.codeLOINC Diagnostic Order CodespreferredLOINC Diagnostic Order Codes
DiagnosticOrder.item.bodySiteSNOMED CT Body StructuresexampleSNOMED CT Body Structures
DiagnosticOrder.item.statusDiagnosticOrderStatusrequiredDiagnosticOrderStatus

K.9.3 Constraints

IdPathDetailsRequirements
.