One Medical FHIR Implementation Guide
0.1.0 - ci-build

One Medical FHIR Implementation Guide - Local Development build (v0.1.0) built by the FHIR (HL7® FHIR® Standard) Build Tools. See the Directory of published versions

Resource Profile: OneLife Condition

Official URL: https://fhir-ig.onemedical.io/StructureDefinition/onelife-condition Version: 0.1.0
Draft as of 2026-05-04 Computable Name: OneLifeCondition

Represents a patient's clinical conditions, problems, and diagnoses as documented by One Medical clinicians. Conditions are recorded on the patient's problem list during clinical encounters and coded using ICD-10-CM, with SNOMED CT cross-maps included when available. Each record tracks clinical status (active, resolved, or inactive) and verification status (confirmed, unconfirmed, provisional, refuted, or entered-in-error) reflecting the clinician's certainty about the diagnosis.

Sensitive conditions (e.g., behavioral health, HIV, substance abuse) carry security labels in meta.security indicating confidentiality level and information sensitivity category. Conditions hidden from the patient portal are tagged with the NOPAT act code.

Consumers should note that clinicalStatus may be absent for unconfirmed, suspected, or rejected conditions — these represent diagnostic uncertainty rather than a known clinical state. The code field always includes an ICD-10-CM coding and may also include a SNOMED CT coding for the same diagnosis.

This profile describes how patient conditions, problems, and diagnoses (e.g., hypertension, diabetes, anxiety) are represented in the One Medical FHIR API.

Conditions are documented by clinicians on the patient's problem list during clinical encounters. Each condition includes a diagnosis code (ICD-10-CM, often with a SNOMED CT cross-map), clinical status, verification status, and a link to the patient record. Sensitive conditions carry security labels indicating confidentiality requirements.

Key Fields

Field What it contains Notes
code The diagnosis (e.g., "Essential hypertension" / ICD-10 I10) Always has an ICD-10-CM coding. SNOMED CT coding included when a cross-map exists. Problems without an ICD-10 code are not synced to FHIR.
clinicalStatus active, resolved, or inactive May be absent for unconfirmed, suspected, or rejected conditions — these represent diagnostic uncertainty, not a known clinical state.
verificationStatus confirmed, unconfirmed, provisional, refuted, or entered-in-error Always present. Reflects the clinician's certainty about the diagnosis.
category Always problem-list-item All OneLife conditions come from the problem list.
subject Reference to the patient Always present.
onsetString When the condition started Free-text string — values like "2019", "childhood", or "since age 30" are common. May be absent.
abatementString When a resolved condition ended Only present for resolved conditions. Contains the resolution date or falls back to the last-updated date.
recordedDate When the condition was entered into the system YYYY-MM-DD format. Distinct from onset (when it started clinically).
recorder Who last edited this condition May reference a Practitioner or a Patient. Absent for system-migrated records.
evidence Link to originating patient survey Only present when the condition was created from a questionnaire submission. Most conditions won't have this.
meta.security Confidentiality and sensitivity labels Present for sensitive conditions (behavioral health, HIV, STD, substance abuse, etc.). See Interpretation Notes below.

Interpretation Notes

  • Absent clinicalStatus — When clinicalStatus is missing, check verificationStatus. Unconfirmed and suspected conditions have no clinical status because the diagnosis itself is uncertain. Rejected conditions have been clinically refuted.
  • entered-in-error — If verificationStatus is entered-in-error, the condition was a mistake and should be ignored entirely by downstream systems.
  • Security labels — Sensitive conditions include meta.security codings from two systems:
    • http://terminology.hl7.org/CodeSystem/v3-Confidentiality: R (restricted) or V (very restricted, used for substance abuse)
    • http://terminology.hl7.org/CodeSystem/v3-ActCode: specific sensitivity category — BH (behavioral health), STD (sexually transmitted disease), SEX (sexuality/reproductive health), HIV (HIV/AIDS), ETH (substance abuse), GDIS (genetic disease), GENDER (gender/sexual orientation), or NOPAT (hidden from patient portal)
  • Multiple codings in code — The coding array may contain both an ICD-10-CM code and one or more SNOMED CT codes for the same diagnosis. Use whichever your downstream system prefers. ICD-10-CM is the authoritative coding.
  • No stage or evidence (staging) — One Medical does not capture structured cancer staging on Condition resources.
  • onset is a string, not a date — Clinicians enter onset as free text, so don't try to parse it as a date.

Usages:

You can also check for usages in the FHIR IG Statistics

Formal Views of Profile Content

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

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Condition C 0..* USCoreCondition(4.0.0) Detailed information about conditions, problems or diagnoses
Constraints: con-3, con-4, con-5, us-core-1
... meta SΣ 1..1 Meta Metadata about the resource
.... source Σ 1..1 uri Identifies where the resource comes from
.... Slices for tag Σ 2..* Coding Tags applied to this resource
Slice: Unordered, Open by pattern:system
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
..... tag:sourceType Σ 1..1 Coding Tags applied to this resource
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
...... system Σ 1..1 uri Identity of the terminology system
Required Pattern: http://onemedical.com/terminology/source-type
...... code Σ 0..1 code Symbol in syntax defined by the system
Required Pattern: one-medical-collected
..... tag:sourceSystem Σ 1..1 Coding Tags applied to this resource
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
...... system Σ 1..1 uri Identity of the terminology system
Required Pattern: http://onemedical.com/terminology/source-system
...... code Σ 0..1 code Symbol in syntax defined by the system
Required Pattern: onelife
... clinicalStatus ?!SΣC 0..1 CodeableConcept Active, resolved, or inactive — absent for unconfirmed/suspected/rejected conditions
Binding: ConditionClinicalStatusCodes (required)
... verificationStatus ?!SΣC 1..1 CodeableConcept Confirmed, unconfirmed, provisional, refuted, or entered-in-error — always present
Binding: ConditionVerificationStatus (required)
... code SΣ 1..1 CodeableConcept ICD-10-CM diagnosis code, often with a SNOMED CT cross-map
Binding: US Core Condition Code (extensible): Valueset to describe the actual problem experienced by the patient
... subject SΣ 1..1 Reference(US Core Patient Profile(4.0.0)) Always references a One Medical patient
... onset[x] SΣ 0..1 string When the condition started — free-text string, often approximate (e.g., '2019' or 'childhood')
... abatement[x] SC 0..1 string Resolution date for resolved conditions — free-text string or fallback to last-updated date
... recordedDate SΣ 0..1 dateTime When this condition was first entered into the system (YYYY-MM-DD)
... recorder SΣ 0..1 Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) The clinician or patient who last edited this condition
... evidence SC 0..1 BackboneElement Link to originating patient survey, if this condition was created from a questionnaire
Constraints: con-2
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... detail SΣC 1..1 Reference(Resource) Reference to the QuestionnaireResponse that originated this condition

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Condition.meta.tag Base example Common Tags 📍4.0.1 FHIR Std.
Condition.meta.tag:sourceType Base example Common Tags 📍4.0.1 FHIR Std.
Condition.meta.tag:sourceSystem Base example Common Tags 📍4.0.1 FHIR Std.
Condition.clinicalStatus Base required Condition Clinical Status Codes 📦4.0.1 FHIR Std.
Condition.verificationStatus Base required ConditionVerificationStatus 📦4.0.1 FHIR Std.
Condition.category Base extensible US Core Condition Category Codes 📦4.0.0 US Core v4.0
Condition.code Base extensible US Core Condition Code 📦4.0.0 US Core v4.0

Constraints

Id Grade Path(s) Description Expression
con-2 error Condition.evidence evidence SHALL have code or details code.exists() or detail.exists()
con-3 best practice Condition Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item clinicalStatus.exists() or verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code = 'entered-in-error').exists() or category.select($this='problem-list-item').empty()
con-4 error Condition If condition is abated, then clinicalStatus must be either inactive, resolved, or remission abatement.empty() or clinicalStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-clinical' and (code='resolved' or code='remission' or code='inactive')).exists()
con-5 error Condition Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code='entered-in-error').empty() or clinicalStatus.empty()
dom-2 error Condition If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-3 error Condition If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4 error Condition If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5 error Condition If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
dom-6 best practice Condition A resource should have narrative for robust management text.`div`.exists()
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1 error **ALL** extensions Must have either extensions or value[x], not both extension.exists() != value.exists()
us-core-1 best practice Condition A code in Condition.category SHOULD be from US Core Condition Category Codes value set. where(category.memberOf('http://hl7.org/fhir/us/core/ValueSet/us-core-condition-category')).exists()

This structure is derived from USCoreCondition

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Condition 0..* USCoreCondition(4.0.0) Detailed information about conditions, problems or diagnoses
... meta S 1..1 Meta Metadata about the resource
.... source 1..1 uri Identifies where the resource comes from
.... Slices for tag 2..* Coding Tags applied to this resource
Slice: Unordered, Open by pattern:system
..... tag:sourceType 1..1 Coding Tags applied to this resource
...... system 1..1 uri Identity of the terminology system
Required Pattern: http://onemedical.com/terminology/source-type
...... code 0..1 code Symbol in syntax defined by the system
Required Pattern: one-medical-collected
..... tag:sourceSystem 1..1 Coding Tags applied to this resource
...... system 1..1 uri Identity of the terminology system
Required Pattern: http://onemedical.com/terminology/source-system
...... code 0..1 code Symbol in syntax defined by the system
Required Pattern: onelife
... implicitRules 0..0 A set of rules under which this content was created
... language 0..0 Language of the resource content
... modifierExtension 0..0 Extension
... clinicalStatus 0..1 CodeableConcept Active, resolved, or inactive — absent for unconfirmed/suspected/rejected conditions
... verificationStatus 1..1 CodeableConcept Confirmed, unconfirmed, provisional, refuted, or entered-in-error — always present
... category 1..* CodeableConcept Always 'problem-list-item' — all OneLife conditions come from the problem list
... severity 0..0 Subjective severity of condition
... code 1..1 CodeableConcept ICD-10-CM diagnosis code, often with a SNOMED CT cross-map
... bodySite 0..0 Anatomical location, if relevant
... subject 1..1 Reference(US Core Patient Profile(4.0.0)) Always references a One Medical patient
... encounter 0..0 Encounter created as part of
... onset[x] S 0..1 string When the condition started — free-text string, often approximate (e.g., '2019' or 'childhood')
... abatement[x] S 0..1 string Resolution date for resolved conditions — free-text string or fallback to last-updated date
... recordedDate S 0..1 dateTime When this condition was first entered into the system (YYYY-MM-DD)
... recorder S 0..1 Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) The clinician or patient who last edited this condition
... asserter 0..0 Person who asserts this condition
... stage 0..0 Stage/grade, usually assessed formally
... evidence S 0..1 BackboneElement Link to originating patient survey, if this condition was created from a questionnaire
.... detail S 1..1 Reference(Resource) Reference to the QuestionnaireResponse that originated this condition
... note 0..0 Additional information about the Condition

doco Documentation for this format
NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Condition C 0..* USCoreCondition(4.0.0) Detailed information about conditions, problems or diagnoses
Constraints: con-3, con-4, con-5, us-core-1
... id Σ 0..1 id Logical id of this artifact
... meta SΣ 1..1 Meta Metadata about the resource
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... versionId Σ 0..1 id Version specific identifier
.... lastUpdated Σ 0..1 instant When the resource version last changed
.... source Σ 1..1 uri Identifies where the resource comes from
.... profile Σ 0..* canonical(StructureDefinition) Profiles this resource claims to conform to
.... security Σ 0..* Coding Security Labels applied to this resource
Binding: All Security Labels (extensible): Security Labels from the Healthcare Privacy and Security Classification System.
.... Slices for tag Σ 2..* Coding Tags applied to this resource
Slice: Unordered, Open by pattern:system
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
..... tag:sourceType Σ 1..1 Coding Tags applied to this resource
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
...... system Σ 1..1 uri Identity of the terminology system
Required Pattern: http://onemedical.com/terminology/source-type
...... version Σ 0..1 string Version of the system - if relevant
...... code Σ 0..1 code Symbol in syntax defined by the system
Required Pattern: one-medical-collected
...... display Σ 0..1 string Representation defined by the system
...... userSelected Σ 0..1 boolean If this coding was chosen directly by the user
..... tag:sourceSystem Σ 1..1 Coding Tags applied to this resource
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
...... system Σ 1..1 uri Identity of the terminology system
Required Pattern: http://onemedical.com/terminology/source-system
...... version Σ 0..1 string Version of the system - if relevant
...... code Σ 0..1 code Symbol in syntax defined by the system
Required Pattern: onelife
...... display Σ 0..1 string Representation defined by the system
...... userSelected Σ 0..1 boolean If this coding was chosen directly by the user
... text 0..1 Narrative Text summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
... identifier Σ 0..* Identifier External Ids for this condition
... clinicalStatus ?!SΣC 0..1 CodeableConcept Active, resolved, or inactive — absent for unconfirmed/suspected/rejected conditions
Binding: ConditionClinicalStatusCodes (required)
... verificationStatus ?!SΣC 1..1 CodeableConcept Confirmed, unconfirmed, provisional, refuted, or entered-in-error — always present
Binding: ConditionVerificationStatus (required)
... category SC 1..* CodeableConcept Always 'problem-list-item' — all OneLife conditions come from the problem list
Binding: US Core Condition Category Codes (extensible)
... code SΣ 1..1 CodeableConcept ICD-10-CM diagnosis code, often with a SNOMED CT cross-map
Binding: US Core Condition Code (extensible): Valueset to describe the actual problem experienced by the patient
... subject SΣ 1..1 Reference(US Core Patient Profile(4.0.0)) Always references a One Medical patient
... onset[x] SΣ 0..1 string When the condition started — free-text string, often approximate (e.g., '2019' or 'childhood')
... abatement[x] SC 0..1 string Resolution date for resolved conditions — free-text string or fallback to last-updated date
... recordedDate SΣ 0..1 dateTime When this condition was first entered into the system (YYYY-MM-DD)
... recorder SΣ 0..1 Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) The clinician or patient who last edited this condition
... evidence SC 0..1 BackboneElement Link to originating patient survey, if this condition was created from a questionnaire
Constraints: con-2
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... code ΣC 0..* CodeableConcept Manifestation/symptom
Binding: ManifestationAndSymptomCodes (example): Codes that describe the manifestation or symptoms of a condition.
.... detail SΣC 1..1 Reference(Resource) Reference to the QuestionnaireResponse that originated this condition

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Condition.meta.security Base extensible SecurityLabels 📍4.0.1 FHIR Std.
Condition.meta.tag Base example Common Tags 📍4.0.1 FHIR Std.
Condition.meta.tag:sourceType Base example Common Tags 📍4.0.1 FHIR Std.
Condition.meta.tag:sourceSystem Base example Common Tags 📍4.0.1 FHIR Std.
Condition.clinicalStatus Base required Condition Clinical Status Codes 📦4.0.1 FHIR Std.
Condition.verificationStatus Base required ConditionVerificationStatus 📦4.0.1 FHIR Std.
Condition.category Base extensible US Core Condition Category Codes 📦4.0.0 US Core v4.0
Condition.code Base extensible US Core Condition Code 📦4.0.0 US Core v4.0
Condition.stage.summary Base example Condition Stage 📦4.0.1 FHIR Std.
Condition.stage.type Base example Condition Stage Type 📦4.0.1 FHIR Std.
Condition.evidence.code Base example Manifestation and Symptom Codes 📦4.0.1 FHIR Std.

Constraints

Id Grade Path(s) Description Expression
con-2 error Condition.evidence evidence SHALL have code or details code.exists() or detail.exists()
con-3 best practice Condition Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item clinicalStatus.exists() or verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code = 'entered-in-error').exists() or category.select($this='problem-list-item').empty()
con-4 error Condition If condition is abated, then clinicalStatus must be either inactive, resolved, or remission abatement.empty() or clinicalStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-clinical' and (code='resolved' or code='remission' or code='inactive')).exists()
con-5 error Condition Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code='entered-in-error').empty() or clinicalStatus.empty()
dom-2 error Condition If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-3 error Condition If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4 error Condition If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5 error Condition If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
dom-6 best practice Condition A resource should have narrative for robust management text.`div`.exists()
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1 error **ALL** extensions Must have either extensions or value[x], not both extension.exists() != value.exists()
us-core-1 best practice Condition A code in Condition.category SHOULD be from US Core Condition Category Codes value set. where(category.memberOf('http://hl7.org/fhir/us/core/ValueSet/us-core-condition-category')).exists()

This structure is derived from USCoreCondition

Summary

Mandatory: 7 elements(1 nested mandatory element)
Must-Support: 7 elements
Prohibited: 10 elements

Slices

This structure defines the following Slices:

  • The element 1 is sliced based on the value of Condition.meta.tag

Key Elements View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Condition C 0..* USCoreCondition(4.0.0) Detailed information about conditions, problems or diagnoses
Constraints: con-3, con-4, con-5, us-core-1
... meta SΣ 1..1 Meta Metadata about the resource
.... source Σ 1..1 uri Identifies where the resource comes from
.... Slices for tag Σ 2..* Coding Tags applied to this resource
Slice: Unordered, Open by pattern:system
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
..... tag:sourceType Σ 1..1 Coding Tags applied to this resource
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
...... system Σ 1..1 uri Identity of the terminology system
Required Pattern: http://onemedical.com/terminology/source-type
...... code Σ 0..1 code Symbol in syntax defined by the system
Required Pattern: one-medical-collected
..... tag:sourceSystem Σ 1..1 Coding Tags applied to this resource
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
...... system Σ 1..1 uri Identity of the terminology system
Required Pattern: http://onemedical.com/terminology/source-system
...... code Σ 0..1 code Symbol in syntax defined by the system
Required Pattern: onelife
... clinicalStatus ?!SΣC 0..1 CodeableConcept Active, resolved, or inactive — absent for unconfirmed/suspected/rejected conditions
Binding: ConditionClinicalStatusCodes (required)
... verificationStatus ?!SΣC 1..1 CodeableConcept Confirmed, unconfirmed, provisional, refuted, or entered-in-error — always present
Binding: ConditionVerificationStatus (required)
... code SΣ 1..1 CodeableConcept ICD-10-CM diagnosis code, often with a SNOMED CT cross-map
Binding: US Core Condition Code (extensible): Valueset to describe the actual problem experienced by the patient
... subject SΣ 1..1 Reference(US Core Patient Profile(4.0.0)) Always references a One Medical patient
... onset[x] SΣ 0..1 string When the condition started — free-text string, often approximate (e.g., '2019' or 'childhood')
... abatement[x] SC 0..1 string Resolution date for resolved conditions — free-text string or fallback to last-updated date
... recordedDate SΣ 0..1 dateTime When this condition was first entered into the system (YYYY-MM-DD)
... recorder SΣ 0..1 Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) The clinician or patient who last edited this condition
... evidence SC 0..1 BackboneElement Link to originating patient survey, if this condition was created from a questionnaire
Constraints: con-2
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... detail SΣC 1..1 Reference(Resource) Reference to the QuestionnaireResponse that originated this condition

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Condition.meta.tag Base example Common Tags 📍4.0.1 FHIR Std.
Condition.meta.tag:sourceType Base example Common Tags 📍4.0.1 FHIR Std.
Condition.meta.tag:sourceSystem Base example Common Tags 📍4.0.1 FHIR Std.
Condition.clinicalStatus Base required Condition Clinical Status Codes 📦4.0.1 FHIR Std.
Condition.verificationStatus Base required ConditionVerificationStatus 📦4.0.1 FHIR Std.
Condition.category Base extensible US Core Condition Category Codes 📦4.0.0 US Core v4.0
Condition.code Base extensible US Core Condition Code 📦4.0.0 US Core v4.0

Constraints

Id Grade Path(s) Description Expression
con-2 error Condition.evidence evidence SHALL have code or details code.exists() or detail.exists()
con-3 best practice Condition Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item clinicalStatus.exists() or verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code = 'entered-in-error').exists() or category.select($this='problem-list-item').empty()
con-4 error Condition If condition is abated, then clinicalStatus must be either inactive, resolved, or remission abatement.empty() or clinicalStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-clinical' and (code='resolved' or code='remission' or code='inactive')).exists()
con-5 error Condition Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code='entered-in-error').empty() or clinicalStatus.empty()
dom-2 error Condition If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-3 error Condition If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4 error Condition If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5 error Condition If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
dom-6 best practice Condition A resource should have narrative for robust management text.`div`.exists()
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1 error **ALL** extensions Must have either extensions or value[x], not both extension.exists() != value.exists()
us-core-1 best practice Condition A code in Condition.category SHOULD be from US Core Condition Category Codes value set. where(category.memberOf('http://hl7.org/fhir/us/core/ValueSet/us-core-condition-category')).exists()

Differential View

This structure is derived from USCoreCondition

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Condition 0..* USCoreCondition(4.0.0) Detailed information about conditions, problems or diagnoses
... meta S 1..1 Meta Metadata about the resource
.... source 1..1 uri Identifies where the resource comes from
.... Slices for tag 2..* Coding Tags applied to this resource
Slice: Unordered, Open by pattern:system
..... tag:sourceType 1..1 Coding Tags applied to this resource
...... system 1..1 uri Identity of the terminology system
Required Pattern: http://onemedical.com/terminology/source-type
...... code 0..1 code Symbol in syntax defined by the system
Required Pattern: one-medical-collected
..... tag:sourceSystem 1..1 Coding Tags applied to this resource
...... system 1..1 uri Identity of the terminology system
Required Pattern: http://onemedical.com/terminology/source-system
...... code 0..1 code Symbol in syntax defined by the system
Required Pattern: onelife
... implicitRules 0..0 A set of rules under which this content was created
... language 0..0 Language of the resource content
... modifierExtension 0..0 Extension
... clinicalStatus 0..1 CodeableConcept Active, resolved, or inactive — absent for unconfirmed/suspected/rejected conditions
... verificationStatus 1..1 CodeableConcept Confirmed, unconfirmed, provisional, refuted, or entered-in-error — always present
... category 1..* CodeableConcept Always 'problem-list-item' — all OneLife conditions come from the problem list
... severity 0..0 Subjective severity of condition
... code 1..1 CodeableConcept ICD-10-CM diagnosis code, often with a SNOMED CT cross-map
... bodySite 0..0 Anatomical location, if relevant
... subject 1..1 Reference(US Core Patient Profile(4.0.0)) Always references a One Medical patient
... encounter 0..0 Encounter created as part of
... onset[x] S 0..1 string When the condition started — free-text string, often approximate (e.g., '2019' or 'childhood')
... abatement[x] S 0..1 string Resolution date for resolved conditions — free-text string or fallback to last-updated date
... recordedDate S 0..1 dateTime When this condition was first entered into the system (YYYY-MM-DD)
... recorder S 0..1 Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) The clinician or patient who last edited this condition
... asserter 0..0 Person who asserts this condition
... stage 0..0 Stage/grade, usually assessed formally
... evidence S 0..1 BackboneElement Link to originating patient survey, if this condition was created from a questionnaire
.... detail S 1..1 Reference(Resource) Reference to the QuestionnaireResponse that originated this condition
... note 0..0 Additional information about the Condition

doco Documentation for this format

Snapshot View

NameFlagsCard.TypeDescription & Constraints    Filter: Filtersdoco
.. Condition C 0..* USCoreCondition(4.0.0) Detailed information about conditions, problems or diagnoses
Constraints: con-3, con-4, con-5, us-core-1
... id Σ 0..1 id Logical id of this artifact
... meta SΣ 1..1 Meta Metadata about the resource
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
.... versionId Σ 0..1 id Version specific identifier
.... lastUpdated Σ 0..1 instant When the resource version last changed
.... source Σ 1..1 uri Identifies where the resource comes from
.... profile Σ 0..* canonical(StructureDefinition) Profiles this resource claims to conform to
.... security Σ 0..* Coding Security Labels applied to this resource
Binding: All Security Labels (extensible): Security Labels from the Healthcare Privacy and Security Classification System.
.... Slices for tag Σ 2..* Coding Tags applied to this resource
Slice: Unordered, Open by pattern:system
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
..... tag:sourceType Σ 1..1 Coding Tags applied to this resource
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
...... system Σ 1..1 uri Identity of the terminology system
Required Pattern: http://onemedical.com/terminology/source-type
...... version Σ 0..1 string Version of the system - if relevant
...... code Σ 0..1 code Symbol in syntax defined by the system
Required Pattern: one-medical-collected
...... display Σ 0..1 string Representation defined by the system
...... userSelected Σ 0..1 boolean If this coding was chosen directly by the user
..... tag:sourceSystem Σ 1..1 Coding Tags applied to this resource
Binding: CommonTags (example): Codes that represent various types of tags, commonly workflow-related; e.g. "Needs review by Dr. Jones".
...... id 0..1 string Unique id for inter-element referencing
...... extension 0..* Extension Additional content defined by implementations
Slice: Unordered, Open by value:url
...... system Σ 1..1 uri Identity of the terminology system
Required Pattern: http://onemedical.com/terminology/source-system
...... version Σ 0..1 string Version of the system - if relevant
...... code Σ 0..1 code Symbol in syntax defined by the system
Required Pattern: onelife
...... display Σ 0..1 string Representation defined by the system
...... userSelected Σ 0..1 boolean If this coding was chosen directly by the user
... text 0..1 Narrative Text summary of the resource, for human interpretation
This profile does not constrain the narrative in regard to content, language, or traceability to data elements
... identifier Σ 0..* Identifier External Ids for this condition
... clinicalStatus ?!SΣC 0..1 CodeableConcept Active, resolved, or inactive — absent for unconfirmed/suspected/rejected conditions
Binding: ConditionClinicalStatusCodes (required)
... verificationStatus ?!SΣC 1..1 CodeableConcept Confirmed, unconfirmed, provisional, refuted, or entered-in-error — always present
Binding: ConditionVerificationStatus (required)
... category SC 1..* CodeableConcept Always 'problem-list-item' — all OneLife conditions come from the problem list
Binding: US Core Condition Category Codes (extensible)
... code SΣ 1..1 CodeableConcept ICD-10-CM diagnosis code, often with a SNOMED CT cross-map
Binding: US Core Condition Code (extensible): Valueset to describe the actual problem experienced by the patient
... subject SΣ 1..1 Reference(US Core Patient Profile(4.0.0)) Always references a One Medical patient
... onset[x] SΣ 0..1 string When the condition started — free-text string, often approximate (e.g., '2019' or 'childhood')
... abatement[x] SC 0..1 string Resolution date for resolved conditions — free-text string or fallback to last-updated date
... recordedDate SΣ 0..1 dateTime When this condition was first entered into the system (YYYY-MM-DD)
... recorder SΣ 0..1 Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) The clinician or patient who last edited this condition
... evidence SC 0..1 BackboneElement Link to originating patient survey, if this condition was created from a questionnaire
Constraints: con-2
.... id 0..1 string Unique id for inter-element referencing
.... extension 0..* Extension Additional content defined by implementations
.... modifierExtension ?!Σ 0..* Extension Extensions that cannot be ignored even if unrecognized
.... code ΣC 0..* CodeableConcept Manifestation/symptom
Binding: ManifestationAndSymptomCodes (example): Codes that describe the manifestation or symptoms of a condition.
.... detail SΣC 1..1 Reference(Resource) Reference to the QuestionnaireResponse that originated this condition

doco Documentation for this format

Terminology Bindings

Path Status Usage ValueSet Version Source
Condition.meta.security Base extensible SecurityLabels 📍4.0.1 FHIR Std.
Condition.meta.tag Base example Common Tags 📍4.0.1 FHIR Std.
Condition.meta.tag:sourceType Base example Common Tags 📍4.0.1 FHIR Std.
Condition.meta.tag:sourceSystem Base example Common Tags 📍4.0.1 FHIR Std.
Condition.clinicalStatus Base required Condition Clinical Status Codes 📦4.0.1 FHIR Std.
Condition.verificationStatus Base required ConditionVerificationStatus 📦4.0.1 FHIR Std.
Condition.category Base extensible US Core Condition Category Codes 📦4.0.0 US Core v4.0
Condition.code Base extensible US Core Condition Code 📦4.0.0 US Core v4.0
Condition.stage.summary Base example Condition Stage 📦4.0.1 FHIR Std.
Condition.stage.type Base example Condition Stage Type 📦4.0.1 FHIR Std.
Condition.evidence.code Base example Manifestation and Symptom Codes 📦4.0.1 FHIR Std.

Constraints

Id Grade Path(s) Description Expression
con-2 error Condition.evidence evidence SHALL have code or details code.exists() or detail.exists()
con-3 best practice Condition Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error and category is problem-list-item clinicalStatus.exists() or verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code = 'entered-in-error').exists() or category.select($this='problem-list-item').empty()
con-4 error Condition If condition is abated, then clinicalStatus must be either inactive, resolved, or remission abatement.empty() or clinicalStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-clinical' and (code='resolved' or code='remission' or code='inactive')).exists()
con-5 error Condition Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error verificationStatus.coding.where(system='http://terminology.hl7.org/CodeSystem/condition-ver-status' and code='entered-in-error').empty() or clinicalStatus.empty()
dom-2 error Condition If the resource is contained in another resource, it SHALL NOT contain nested Resources contained.contained.empty()
dom-3 error Condition If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().as(canonical) | %resource.descendants().as(uri) | %resource.descendants().as(url))) or descendants().where(reference = '#').exists() or descendants().where(as(canonical) = '#').exists() or descendants().where(as(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
dom-4 error Condition If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
dom-5 error Condition If a resource is contained in another resource, it SHALL NOT have a security label contained.meta.security.empty()
dom-6 best practice Condition A resource should have narrative for robust management text.`div`.exists()
ele-1 error **ALL** elements All FHIR elements must have a @value or children hasValue() or (children().count() > id.count())
ext-1 error **ALL** extensions Must have either extensions or value[x], not both extension.exists() != value.exists()
us-core-1 best practice Condition A code in Condition.category SHOULD be from US Core Condition Category Codes value set. where(category.memberOf('http://hl7.org/fhir/us/core/ValueSet/us-core-condition-category')).exists()

This structure is derived from USCoreCondition

Summary

Mandatory: 7 elements(1 nested mandatory element)
Must-Support: 7 elements
Prohibited: 10 elements

Slices

This structure defines the following Slices:

  • The element 1 is sliced based on the value of Condition.meta.tag

 

Other representations of profile: CSV, Excel, Schematron