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.

K.12 StructureDefinition: GAO Procedure Request

The official URL for this profile is: 

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

Profiles the procedure request 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.12.1 Formal Views of Profile Content

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

This structure is derived from ProcedureRequest.

Summary

Mandatory: 1 element (+1 nested mandatory element)

This structure is derived from ProcedureRequest.

NameFlagsCard.TypeDescription & Constraintsdoco
.. ProcedureRequest ∑0..*ProcedureRequestA request for a procedure to be performed
... 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
... identifier ∑0..*IdentifierUnique identifier for the request
... subject ∑1..1Reference(Patient | Group)Who the procedure should be done to
... code ∑1..1CodeableConceptWhat procedure to perform
Binding: Procedure Codes (SNOMED CT) (example)
... bodySite ∑0..*CodeableConceptWhat part of body to perform on
Binding: SNOMED CT Body Structures (example)
... reason[x] ∑1..1CodeableConcept, Reference(Condition)Why procedure should occur
Binding: Procedure Reason Codes (example)
... scheduled[x] ∑0..1dateTime, Period, TimingWhen procedure should occur
... encounter ∑0..1Reference(Encounter)Encounter request created during
... performer ∑0..1Reference(Practitioner | Organization | Patient | RelatedPerson)Who should perform the procedure
... status ?! ∑0..1codeproposed | draft | requested | received | accepted | in-progress | completed | suspended | rejected | aborted
Binding: ProcedureRequestStatus (required)
... notes ∑0..*AnnotationAdditional information about desired procedure
... asNeeded[x] ∑0..1boolean, CodeableConceptPreconditions for procedure
Binding: (unbound) (example)
... orderedOn ∑0..1dateTimeWhen request was created
... orderer ∑0..1Reference(Practitioner | Patient | RelatedPerson | Device)Who made request
... priority ∑0..1coderoutine | urgent | stat | asap
Binding: ProcedureRequestPriority (required)

doco Documentation for this format

todo

This structure is derived from ProcedureRequest.

Summary

Mandatory: 1 element (+1 nested mandatory element)

Differential View

This structure is derived from ProcedureRequest.

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. ProcedureRequest ∑0..*ProcedureRequestA request for a procedure to be performed
... 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
... identifier ∑0..*IdentifierUnique identifier for the request
... subject ∑1..1Reference(Patient | Group)Who the procedure should be done to
... code ∑1..1CodeableConceptWhat procedure to perform
Binding: Procedure Codes (SNOMED CT) (example)
... bodySite ∑0..*CodeableConceptWhat part of body to perform on
Binding: SNOMED CT Body Structures (example)
... reason[x] ∑1..1CodeableConcept, Reference(Condition)Why procedure should occur
Binding: Procedure Reason Codes (example)
... scheduled[x] ∑0..1dateTime, Period, TimingWhen procedure should occur
... encounter ∑0..1Reference(Encounter)Encounter request created during
... performer ∑0..1Reference(Practitioner | Organization | Patient | RelatedPerson)Who should perform the procedure
... status ?! ∑0..1codeproposed | draft | requested | received | accepted | in-progress | completed | suspended | rejected | aborted
Binding: ProcedureRequestStatus (required)
... notes ∑0..*AnnotationAdditional information about desired procedure
... asNeeded[x] ∑0..1boolean, CodeableConceptPreconditions for procedure
Binding: (unbound) (example)
... orderedOn ∑0..1dateTimeWhen request was created
... orderer ∑0..1Reference(Practitioner | Patient | RelatedPerson | Device)Who made request
... priority ∑0..1coderoutine | urgent | stat | asap
Binding: ProcedureRequestPriority (required)

doco Documentation for this format

XML Template

JSON Template

todo

 

Other representations of profile: Schematron

K.12.2 Terminology Bindings

PathNameConformanceValueSet
ProcedureRequest.language?extrequiredhttp://tools.ietf.org/html/bcp47
ProcedureRequest.codeProcedure Codes (SNOMED CT)exampleProcedure Codes (SNOMED CT)
ProcedureRequest.bodySiteSNOMED CT Body StructuresexampleSNOMED CT Body Structures
ProcedureRequest.reason[x]Procedure Reason CodesexampleProcedure Reason Codes
ProcedureRequest.statusProcedureRequestStatusrequiredProcedureRequestStatus
ProcedureRequest.asNeeded[x]?extexample
ProcedureRequest.priorityProcedureRequestPriorityrequiredProcedureRequestPriority

K.12.3 Constraints

IdPathDetailsRequirements
.