GAO Ballot Package

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

This is a frozen snapshot of the FHIR specification created for the purpose of balloting the GAO implementation Guide. It includes draft changes that may be part of the future DSTU 2.1 release but further change is expected. Readers should focus solely on the GAO implementation content, and FHIR DSTU 2 for other purposes.

D.5.1 StructureDefinition: DAF-DiagnosticOrder

The official URL for this profile is: 

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

Defines constraints and extensions on the DiagnosticOrder resource for use in querying and retrieving DiagnosticOrder information.

This profile was published on Thu, Aug 21, 2014 00:00+1000 as a draft by Health Level Seven International (Infrastructure and Messaging - Data Access Framework).

D.5.1.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: 16 elements (+3 nested mandatory elements)
Must-Support: 25 elements
Fixed Value: 1 element

Structures

This structure refers to these other structures:

Slices

This structure defines the following Slices:

  • The element DiagnosticOrder.supportingInformation is sliced based on the values of @Profile
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 S ∑1..1Reference(DAF-Patient)Who and/or what test is about
... orderer S ∑1..1Reference(DAF-Pract)Who ordered the test
... identifier S ∑0..*IdentifierIdentifiers assigned to this order
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?! S∑1..1codeusual | official | temp | secondary (If known)
Binding: IdentifierUse (required)
Fixed Value: official
.... type ∑0..1CodeableConceptDescription of identifier
Binding: Identifier Type Codes (extensible)
.... system S ∑1..1uriThe namespace for the identifier
Example: http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri
.... value S ∑1..1stringThe value that is unique
Example: 123456
.... period ∑0..1PeriodTime period when id is/was valid for use
.... assigner ∑0..1Reference(Organization)Organization that issued id (may be just text)
... encounter S ∑0..1Reference(DAF-Encounter)The encounter that this diagnostic order is associated with
... reason S0..*CodeableConceptExplanation/Justification for test
Binding: Condition/Problem/Diagnosis Codes (example)
... supportingInformation Reference(Observation | Condition | DocumentReference)Additional clinical information
Slice: Unordered, Open, by @Profile, @type
... supportingInformation S0..*Reference(DAF-ResultObs | DAF-Condition)Additional clinical information
... specimen 0..*Reference(Specimen)If the whole order relates to specific specimens
... status ?! S∑1..1codeproposed | draft | planned | requested | received | accepted | in-progress | review | completed | cancelled | suspended | rejected | failed
Binding: DiagnosticOrderStatus (required)
... priority S ∑1..1coderoutine | urgent | stat | asap
Binding: DiagnosticOrderPriority (required)
... event S1..*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 S ∑1..1CodeableConceptMore information about the event and its context
Binding: USLAB Diagnostic Order Event Codes (extensible)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... coding S ∑1..1CodingCode defined by a terminology system
...... extension 0..*ExtensionAdditional Content defined by implementations
...... system S ∑1..1uriIdentity of the terminology system
...... version ∑0..1stringVersion of the system - if relevant
...... code S ∑1..1codeSymbol in syntax defined by the system
...... display ∑0..1stringRepresentation defined by the system
...... userSelected ∑0..1booleanIf this coding was chosen directly by the user
..... text ∑0..1stringPlain text representation of the concept
.... dateTime S ∑1..1dateTimeThe date at which the event happened
.... actor 0..1Reference(Practitioner | Device)Who recorded or did this
... item S1..*BackboneElementThe items the orderer requested
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... code S ∑1..1CodeableConceptUS Realm Laboratory Report Order Code
Binding: US Laboratory Observation Profile Observation Name Codes (extensible)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... coding S ∑1..*CodingStandard and local codes may be included here by repeating the coding element with a different coding.system.
...... extension 0..*ExtensionAdditional Content defined by implementations
...... system S ∑1..1uriIdentity of the terminology system
...... version ∑0..1stringVersion of the system - if relevant
...... code S ∑1..1codeSymbol in syntax defined by the system
...... display S ∑0..1stringRepresentation defined by the system
...... userSelected ∑0..1booleanIf this coding was chosen directly by the user
..... text S ∑0..1stringPlain text representation of the concept
.... specimen 0..*Reference(Specimen)If this item relates to specific specimens
.... bodySite 0..1CodeableConceptLocation of requested test (if applicable)
Binding: SNOMED CT Body Structures (example)
.... status S ∑1..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 0..*AnnotationOther notes and comments

doco Documentation for this format

todo

This structure is derived from DiagnosticOrder.

Summary

Mandatory: 16 elements (+3 nested mandatory elements)
Must-Support: 25 elements
Fixed Value: 1 element

Structures

This structure refers to these other structures:

Slices

This structure defines the following Slices:

  • The element DiagnosticOrder.supportingInformation is sliced based on the values of @Profile

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 S ∑1..1Reference(DAF-Patient)Who and/or what test is about
... orderer S ∑1..1Reference(DAF-Pract)Who ordered the test
... identifier S ∑0..*IdentifierIdentifiers assigned to this order
.... extension 0..*ExtensionAdditional Content defined by implementations
.... use ?! S∑1..1codeusual | official | temp | secondary (If known)
Binding: IdentifierUse (required)
Fixed Value: official
.... type ∑0..1CodeableConceptDescription of identifier
Binding: Identifier Type Codes (extensible)
.... system S ∑1..1uriThe namespace for the identifier
Example: http://www.acme.com/identifiers/patient or urn:ietf:rfc:3986 if the Identifier.value itself is a full uri
.... value S ∑1..1stringThe value that is unique
Example: 123456
.... period ∑0..1PeriodTime period when id is/was valid for use
.... assigner ∑0..1Reference(Organization)Organization that issued id (may be just text)
... encounter S ∑0..1Reference(DAF-Encounter)The encounter that this diagnostic order is associated with
... reason S0..*CodeableConceptExplanation/Justification for test
Binding: Condition/Problem/Diagnosis Codes (example)
... supportingInformation Reference(Observation | Condition | DocumentReference)Additional clinical information
Slice: Unordered, Open, by @Profile, @type
... supportingInformation S0..*Reference(DAF-ResultObs | DAF-Condition)Additional clinical information
... specimen 0..*Reference(Specimen)If the whole order relates to specific specimens
... status ?! S∑1..1codeproposed | draft | planned | requested | received | accepted | in-progress | review | completed | cancelled | suspended | rejected | failed
Binding: DiagnosticOrderStatus (required)
... priority S ∑1..1coderoutine | urgent | stat | asap
Binding: DiagnosticOrderPriority (required)
... event S1..*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 S ∑1..1CodeableConceptMore information about the event and its context
Binding: USLAB Diagnostic Order Event Codes (extensible)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... coding S ∑1..1CodingCode defined by a terminology system
...... extension 0..*ExtensionAdditional Content defined by implementations
...... system S ∑1..1uriIdentity of the terminology system
...... version ∑0..1stringVersion of the system - if relevant
...... code S ∑1..1codeSymbol in syntax defined by the system
...... display ∑0..1stringRepresentation defined by the system
...... userSelected ∑0..1booleanIf this coding was chosen directly by the user
..... text ∑0..1stringPlain text representation of the concept
.... dateTime S ∑1..1dateTimeThe date at which the event happened
.... actor 0..1Reference(Practitioner | Device)Who recorded or did this
... item S1..*BackboneElementThe items the orderer requested
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension ?!0..*ExtensionExtensions that cannot be ignored
.... code S ∑1..1CodeableConceptUS Realm Laboratory Report Order Code
Binding: US Laboratory Observation Profile Observation Name Codes (extensible)
..... extension 0..*ExtensionAdditional Content defined by implementations
..... coding S ∑1..*CodingStandard and local codes may be included here by repeating the coding element with a different coding.system.
...... extension 0..*ExtensionAdditional Content defined by implementations
...... system S ∑1..1uriIdentity of the terminology system
...... version ∑0..1stringVersion of the system - if relevant
...... code S ∑1..1codeSymbol in syntax defined by the system
...... display S ∑0..1stringRepresentation defined by the system
...... userSelected ∑0..1booleanIf this coding was chosen directly by the user
..... text S ∑0..1stringPlain text representation of the concept
.... specimen 0..*Reference(Specimen)If this item relates to specific specimens
.... bodySite 0..1CodeableConceptLocation of requested test (if applicable)
Binding: SNOMED CT Body Structures (example)
.... status S ∑1..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 0..*AnnotationOther notes and comments

doco Documentation for this format

XML Template

JSON Template

todo

 

Other representations of profile: Schematron

D.5.1.2 Terminology Bindings

PathNameConformanceValueSet
DiagnosticOrder.language?extrequiredhttp://tools.ietf.org/html/bcp47
DiagnosticOrder.identifier.useIdentifierUserequiredIdentifierUse
DiagnosticOrder.identifier.typeIdentifier Type CodesextensibleIdentifier Type Codes
DiagnosticOrder.reasonCondition/Problem/Diagnosis CodesexampleCondition/Problem/Diagnosis Codes
DiagnosticOrder.statusDiagnosticOrderStatusrequiredDiagnosticOrderStatus
DiagnosticOrder.priorityDiagnosticOrderPriorityrequiredDiagnosticOrderPriority
DiagnosticOrder.event.statusDiagnosticOrderStatusrequiredDiagnosticOrderStatus
DiagnosticOrder.event.descriptionUSLAB Diagnostic Order Event CodesextensibleUSLAB Diagnostic Order Event Codes
DiagnosticOrder.item.codeUS Laboratory Observation Profile Observation Name CodesextensibleUS Laboratory Observation Profile Observation Name Codes
DiagnosticOrder.item.bodySiteSNOMED CT Body StructuresexampleSNOMED CT Body Structures
DiagnosticOrder.item.statusDiagnosticOrderStatusrequiredDiagnosticOrderStatus

D.5.1.3 Constraints

IdPathDetailsRequirements
.