This page is part of the FHIR Specification (v0.0.82: DSTU 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

StructureDefinition: USlabReasonForStudy

The official URL for this profile is: 

http://hl7.org/fhir/StructureDefinition/cond-uslab-uslabreasonforstudy

The Condition(s) referenced in USRealm laboratory test and reporting in ambulatory care setting.

This profile was published on Mon, Nov 17, 2014 00:00+1100 as a draft by HL7 International - Orders and Observations WG.

Formal Views of Profile Content

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

This structure is derived from Condition.

Summary

Terminology Bindings

  • Condition.code SHALL come from This value set includes all ICD-9CM and ICD-10CM concept codes

Required/Prohibited Elements

  • The element Condition.patient is required
  • The element Condition.code is required
  • The element Condition.code.coding is required
  • The element Condition.code.coding.code is required
  • The element Condition.code.coding.system is required
  • The element Condition.category is required
  • The element Condition.category.coding.code is required
  • The element Condition.category.coding.system is required
  • The element Condition.clinicalStatus is required

This structure is derived from Condition.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Condition 1..1ConditionReason for Study or Additional Clinical Information for Laboratorian or Pathologist.
... patient S1..1patient-uslab-uslabpatient, patient-uslab-uslabphpatientPatient
... code S1..1CodeableConceptBinding: USlabReasonForStudy (required)
.... coding S1..1
..... code S1..1
..... display S0..1
..... system S1..1
... category S1..1
.... coding S0..1
..... code S1..1
..... display S0..1
..... system S1..1
... clinicalStatus S1..1
NameFlagsCard.TypeDescription & Constraintsdoco
.. Condition 1..1ConditionReason for Study or Additional Clinical Information for Laboratorian or Pathologist.
... 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: Language (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..*IdentifierExternal Ids for this condition
... patient S1..1patient-uslab-uslabpatient, patient-uslab-uslabphpatientPatient
... encounter 0..1EncounterEncounter when condition first asserted
... asserter 0..1Practitioner, PatientPerson who asserts this condition
... dateAsserted 0..1dateWhen first detected/suspected/entered
... code S1..1CodeableConceptIdentification of the condition, problem or diagnosis
Binding: USlabReasonForStudy (required)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... coding S1..1CodingCode defined by a terminology system
..... extension 0..*ExtensionAdditional Content defined by implementations
..... system S1..1uriIdentity of the terminology system
..... version 0..1stringVersion of the system - if relevant
..... code 0..1codeSymbol in syntax defined by the system
..... display 0..1stringRepresentation defined by the system
..... primary 0..1booleanIf this code was chosen directly by the user
.... text 0..1stringPlain text representation of the concept
... category S1..1CodeableConceptE.g. complaint | symptom | finding | diagnosis
Binding: ConditionCategory (required)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... coding S0..1CodingCode defined by a terminology system
..... extension 0..*ExtensionAdditional Content defined by implementations
..... system S1..1uriIdentity of the terminology system
..... version 0..1stringVersion of the system - if relevant
..... code 0..1codeSymbol in syntax defined by the system
..... display 0..1stringRepresentation defined by the system
..... primary 0..1booleanIf this code was chosen directly by the user
.... text 0..1stringPlain text representation of the concept
... clinicalStatus ?! S1..1codeprovisional | working | confirmed | refuted | entered-in-error | unknown
Binding: ConditionClinicalStatus (required)
... severity 0..1CodeableConceptSubjective severity of condition
Binding: ConditionSeverity (example)
... onset[x] 0..1dateTime, Age, Period, Range, stringEstimated or actual date, date-time, or age
... abatement[x] 0..1date, Age, boolean, Period, Range, stringIf/when in resolution/remission
... stage I0..1Stage/grade, usually assessed formally
con-1: Stage SHALL have summary or assessment
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... summary I0..1CodeableConceptSimple summary (disease specific)
.... assessment I0..*ResourceFormal record of assessment
... evidence I0..*Supporting evidence
con-2: evidence SHALL have code or details
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... code I0..1CodeableConceptManifestation/symptom
.... detail I0..*ResourceSupporting information found elsewhere
... location I0..*Anatomical location, if relevant
con-3: location SHALL have code or details
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... code I0..1CodeableConceptLocation - may include laterality
.... detail I0..1stringPrecise location details
... dueTo I0..*Causes for this Condition
con-4: Relationship SHALL have either a code or a target
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... code I0..1CodeableConceptRelationship target by means of a predefined code
Binding: ConditionKind (example)
.... target I0..1Condition, Procedure, MedicationAdministration, Immunization, MedicationStatementRelationship target resource
... occurredFollowing I0..*Precedent for this Condition
con-5: Relationship SHALL have either a code or a target
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... code I0..1CodeableConceptRelationship target by means of a predefined code
Binding: ConditionKind (example)
.... target I0..1Condition, Procedure, MedicationAdministration, Immunization, MedicationStatementRelationship target resource
... notes 0..1stringAdditional information about the Condition

todo

This structure is derived from Condition.

Summary

Terminology Bindings

  • Condition.code SHALL come from This value set includes all ICD-9CM and ICD-10CM concept codes

Required/Prohibited Elements

  • The element Condition.patient is required
  • The element Condition.code is required
  • The element Condition.code.coding is required
  • The element Condition.code.coding.code is required
  • The element Condition.code.coding.system is required
  • The element Condition.category is required
  • The element Condition.category.coding.code is required
  • The element Condition.category.coding.system is required
  • The element Condition.clinicalStatus is required

Differential View

This structure is derived from Condition.

NameFlagsCard.TypeDescription & Constraintsdoco
.. Condition 1..1ConditionReason for Study or Additional Clinical Information for Laboratorian or Pathologist.
... patient S1..1patient-uslab-uslabpatient, patient-uslab-uslabphpatientPatient
... code S1..1CodeableConceptBinding: USlabReasonForStudy (required)
.... coding S1..1
..... code S1..1
..... display S0..1
..... system S1..1
... category S1..1
.... coding S0..1
..... code S1..1
..... display S0..1
..... system S1..1
... clinicalStatus S1..1

Snapshot View

NameFlagsCard.TypeDescription & Constraintsdoco
.. Condition 1..1ConditionReason for Study or Additional Clinical Information for Laboratorian or Pathologist.
... 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: Language (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..*IdentifierExternal Ids for this condition
... patient S1..1patient-uslab-uslabpatient, patient-uslab-uslabphpatientPatient
... encounter 0..1EncounterEncounter when condition first asserted
... asserter 0..1Practitioner, PatientPerson who asserts this condition
... dateAsserted 0..1dateWhen first detected/suspected/entered
... code S1..1CodeableConceptIdentification of the condition, problem or diagnosis
Binding: USlabReasonForStudy (required)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... coding S1..1CodingCode defined by a terminology system
..... extension 0..*ExtensionAdditional Content defined by implementations
..... system S1..1uriIdentity of the terminology system
..... version 0..1stringVersion of the system - if relevant
..... code 0..1codeSymbol in syntax defined by the system
..... display 0..1stringRepresentation defined by the system
..... primary 0..1booleanIf this code was chosen directly by the user
.... text 0..1stringPlain text representation of the concept
... category S1..1CodeableConceptE.g. complaint | symptom | finding | diagnosis
Binding: ConditionCategory (required)
.... extension 0..*ExtensionAdditional Content defined by implementations
.... coding S0..1CodingCode defined by a terminology system
..... extension 0..*ExtensionAdditional Content defined by implementations
..... system S1..1uriIdentity of the terminology system
..... version 0..1stringVersion of the system - if relevant
..... code 0..1codeSymbol in syntax defined by the system
..... display 0..1stringRepresentation defined by the system
..... primary 0..1booleanIf this code was chosen directly by the user
.... text 0..1stringPlain text representation of the concept
... clinicalStatus ?! S1..1codeprovisional | working | confirmed | refuted | entered-in-error | unknown
Binding: ConditionClinicalStatus (required)
... severity 0..1CodeableConceptSubjective severity of condition
Binding: ConditionSeverity (example)
... onset[x] 0..1dateTime, Age, Period, Range, stringEstimated or actual date, date-time, or age
... abatement[x] 0..1date, Age, boolean, Period, Range, stringIf/when in resolution/remission
... stage I0..1Stage/grade, usually assessed formally
con-1: Stage SHALL have summary or assessment
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... summary I0..1CodeableConceptSimple summary (disease specific)
.... assessment I0..*ResourceFormal record of assessment
... evidence I0..*Supporting evidence
con-2: evidence SHALL have code or details
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... code I0..1CodeableConceptManifestation/symptom
.... detail I0..*ResourceSupporting information found elsewhere
... location I0..*Anatomical location, if relevant
con-3: location SHALL have code or details
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... code I0..1CodeableConceptLocation - may include laterality
.... detail I0..1stringPrecise location details
... dueTo I0..*Causes for this Condition
con-4: Relationship SHALL have either a code or a target
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... code I0..1CodeableConceptRelationship target by means of a predefined code
Binding: ConditionKind (example)
.... target I0..1Condition, Procedure, MedicationAdministration, Immunization, MedicationStatementRelationship target resource
... occurredFollowing I0..*Precedent for this Condition
con-5: Relationship SHALL have either a code or a target
.... extension 0..*ExtensionAdditional Content defined by implementations
.... modifierExtension 0..*ExtensionExtensions that cannot be ignored
.... code I0..1CodeableConceptRelationship target by means of a predefined code
Binding: ConditionKind (example)
.... target I0..1Condition, Procedure, MedicationAdministration, Immunization, MedicationStatementRelationship target resource
... notes 0..1stringAdditional information about the Condition

XML Template

JSON Template

todo

 

Other representations of profile: (todo)

Terminology Bindings

PathNameConformanceValueSet
Condition.languageLanguagerequiredhttp://tools.ietf.org/html/bcp47
Condition.codeUSlabReasonForStudyrequiredUSlabConditonCodes
Condition.categoryConditionCategoryrequiredCondition/Problem/Diagnosis Codes
Condition.clinicalStatusConditionClinicalStatusrequiredConditionClinicalStatus
Condition.severityConditionSeverityexampleCondition/Diagnosis Severity
Condition.dueTo.codeConditionKindexampleCondition/Problem/Diagnosis Codes
Condition.occurredFollowing.codeConditionKindexampleCondition/Problem/Diagnosis Codes

Constraints

IdPathNameDetails
con-1Condition.stageStage ruleStage SHALL have summary or assessment
XPath: exists(f:summary) or exists(f:assessment)
con-2Condition.evidenceEvidenceevidence SHALL have code or details
XPath: exists(f:code) or exists(f:detail)
con-3Condition.locationLocationlocation SHALL have code or details
XPath: exists(f:code) or exists(f:detail)
con-4Condition.dueToRelationship1Relationship SHALL have either a code or a target
XPath: exists(f:code) != exists(f:target)
con-5Condition.occurredFollowingRelationship2Relationship SHALL have either a code or a target
XPath: exists(f:code) != exists(f:target)
.