| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | L Type | L Description & Constraints | Comments |
|---|
  Condition | C | 0..* | Condition | Argonaut Condition Profile
arg-1: Condition.clinicalStatus SHALL be present if verificationStatus is not entered-in-error. Condition.clinicalStatus SHALL NOT be present if verification Status is entered-in-error
| C | 0..* | Condition | Detailed information about conditions, problems or diagnoses
| - Elements differ in short: 'Argonaut Condition Profile' vs 'Detailed information about conditions, problems or diagnoses'
- Elements differ in definition: 'Use to record detailed information about conditions, problems or diagnoses recognized by a clinician. There are many uses including: recording a diagnosis during an encounter; populating a problem list or a summary statement, such as a discharge summary.' vs '\-'
|
 id | Σ | 0..1 | id | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact | - Elements differ in comments: 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Bundles always have an id, though it is usually a generated UUID.' vs 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.'
|
| meta | Σ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource | - Elements differ in definition: 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.' vs 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to the resource.'
|
| implicitRules | ?!Σ | 0..1 | uri | A set of rules under which this content was created | ?!Σ | 0..1 | uri | A set of rules under which this content was created | - Elements differ in definition: 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.' vs 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.'
- Elements differ in comments: 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible.' vs 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.'
|
| language | | 0..1 | code | Language of the resource content
Binding: todo (required): A human language.
| | 0..1 | code | Language of the resource content
Binding: todo (preferred): A human language.
| - Elements differ in comments: 'Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).' vs 'Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).'
|
| text | | 0..1 | Narrative | Text summary of the resource, for human interpretation | | 0..1 | Narrative | Text summary of the resource, for human interpretation | - Elements differ in definition: 'A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.' vs 'A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.'
- Elements differ in comments: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.'
|
| contained | | 0..* | Resource | Contained, inline Resources
| | 0..* | Resource | Contained, inline Resources
| - Elements differ in comments: 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.' vs 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.'
|
 extension | | 0..* | Extension | Additional Content defined by implementations
| | 0..* | Extension | Extension
Slice: Unordered, Open by value:url
| - Elements differ in short: 'Additional Content defined by implementations' vs 'Extension'
- Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'An Extension'
|
 modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored
| ?! | 0..* | Extension | Extensions that cannot be ignored
| - Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
|
| identifier | Σ | 0..* | Identifier | External Ids for this condition
| Σ | 0..* | Identifier | External Ids for this condition
| - Elements differ in definition: 'This records identifiers associated with this condition that are defined by business processes and/or used to refer to it when a direct URL reference to the resource itself is not appropriate (e.g. in CDA documents, or in written / printed documentation).' vs 'Business identifiers assigned to this condition by the performer or other systems which remain constant as the resource is updated and propagates from server to server.'
- Elements differ in requirements: 'Need to allow connection to a wider workflow.' vs 'Allows identification of the condition as it is known by various participating systems and in a way that remains consistent across servers.'
|
| patient | S | 1..1 | Reference(http://fhir.org/guides/argonaut/StructureDefinition/argo-patient) | Who has the condition? | | | | | |
| encounter | Σ | 0..1 | Reference(Encounter) | Encounter when condition first asserted | Σ | 0..1 | Reference(Encounter) | Encounter created as part of | - Elements differ in short: 'Encounter when condition first asserted' vs 'Encounter created as part of'
- Elements differ in definition: 'Encounter during which the condition was first asserted.' vs 'The Encounter during which this Condition was created or to which the creation of this record is tightly associated.'
- Elements differ in comments: 'This record indicates the encounter this particular record is associated with. In the case of a "new" diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first "known".' vs 'This will typically be the encounter the event occurred within, but some activities may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter. This record indicates the encounter this particular record is associated with. In the case of a "new" diagnosis reflecting ongoing/revised information about the condition, this might be distinct from the first encounter in which the underlying condition was first "known".'
|
| asserter | Σ | 0..1 | Reference(Practitioner | Patient) | Person who asserts this condition | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) | Person who asserts this condition | |
| dateRecorded | Σ | 0..1 | date | When first entered | | | | | |
| code | S | 1..1 | CodeableConcept | Identification of the condition, problem or diagnosis
Binding: todo (extensible): Valueset to describe the actual problem experienced by the patient
| SΣ | 1..1 | CodeableConcept | (USCDI) Identification of the condition, problem or diagnosis
Binding: todo (extensible): Valueset to describe the actual problem experienced by the patient
| - Elements differ in short: 'Identification of the condition, problem or diagnosis' vs '(USCDI) Identification of the condition, problem or diagnosis'
- Unable to resolve left value set http://hl7.org/fhir/ValueSet/daf-problem at Condition.code
|
| category | | 1..1 | CodeableConcept | complaint | symptom | finding | diagnosis
Binding: todo (preferred): Extended category code valueset to support the intent of the separate concepts of problems and health concerns
| S | 1..* | CodeableConcept | (USCDI) category codes
Slice: Unordered, Open by pattern:$this
Binding: todo (extensible): A category assigned to the condition.
| - Elements differ in short: 'complaint | symptom | finding | diagnosis' vs '(USCDI) category codes'
- Elements differ in definition for mustSupport: 'false' vs 'true'
- Element maximum cardinalities differ: '1' vs '2147483647'
- Elements differ in binding.description: 'Extended category code valueset to support the intent of the separate concepts of problems and health concerns' vs 'A category assigned to the condition.'
|
| clinicalStatus | ?!S | 0..1 | code | active | relapse | remission | resolved
Binding: todo (required) | ?!SΣC | 0..1 | CodeableConcept | (USCDI) active | recurrence | relapse | inactive | remission | resolved
Binding: todo (required) | - Elements differ in short: 'active | relapse | remission | resolved' vs '(USCDI) active | recurrence | relapse | inactive | remission | resolved'
|
| verificationStatus | ?!S | 1..1 | code | provisional | differential | confirmed | refuted | entered-in-error | unknown
Binding: todo (required) | ?!SΣC | 0..1 | CodeableConcept | (USCDI) unconfirmed | provisional | differential | confirmed | refuted | entered-in-error
Binding: todo (required) | - Elements differ in short: 'provisional | differential | confirmed | refuted | entered-in-error | unknown' vs '(USCDI) unconfirmed | provisional | differential | confirmed | refuted | entered-in-error'
- Element minimum cardinalities differ: '1' vs '0'
|
| severity | Σ | 0..1 | CodeableConcept | Subjective severity of condition
Binding: todo (preferred): A subjective assessment of the severity of the condition as evaluated by the clinician.
| | 0..1 | CodeableConcept | Subjective severity of condition
Binding: todo (preferred): A subjective assessment of the severity of the condition as evaluated by the clinician.
| |
| onset[x] | Σ | 0..1 | dateTime, Quantity, Period, Range, string | Estimated or actual date, date-time, or age | SΣ | 0..1 | dateTime S, Age, Period, Range, string | (USCDI) Estimated or actual date, date-time, or age | - Elements differ in short: 'Estimated or actual date, date-time, or age' vs '(USCDI) Estimated or actual date, date-time, or age'
- Elements differ in definition for mustSupport: 'false' vs 'true'
|
| abatement[x] | Σ | 0..1 | dateTime, Quantity, boolean, Period, Range, string | If/when in resolution/remission | SC | 0..1 | dateTime S, Age, Period, Range, string | (USCDI) When in resolution/remission | - Elements differ in short: 'If/when in resolution/remission' vs '(USCDI) When in resolution/remission'
- Elements differ in comments: 'There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid.' vs 'There is no explicit distinction between resolution and remission because in many cases the distinction is not clear. Age is generally used when the patient reports an age at which the Condition abated. If there is no abatement element, it is unknown whether the condition has resolved or entered remission; applications and users should generally assume that the condition is still valid. When abatementString exists, it implies the condition is abated.'
- Elements differ in definition for mustSupport: 'false' vs 'true'
|
| stage | ΣC | 0..1 | BackboneElement | Stage/grade, usually assessed formally
con-1: Stage SHALL have summary or assessment | C | 0..* | BackboneElement | Stage/grade, usually assessed formally
| - Element maximum cardinalities differ: '1' vs '2147483647'
|
 id | | 0..1 | id | xml:id (or equivalent in JSON) | | 0..1 | string | Unique id for inter-element referencing | - Elements differ in short: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
- Elements differ in definition: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
|
| extension | | 0..* | Extension | Additional Content defined by implementations
| | 0..* | Extension | Additional content defined by implementations
| - Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
|
| modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored
| ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized
| - Elements differ in short: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized'
- Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
|
| summary | ΣC | 0..1 | CodeableConcept | Simple summary (disease specific)
Binding: todo (example): Codes describing condition stages (e.g. Cancer stages).
| C | 0..1 | CodeableConcept | Simple summary (disease specific)
Binding: todo (example): Codes describing condition stages (e.g. Cancer stages).
| |
| assessment | ΣC | 0..* | Reference(ClinicalImpression | DiagnosticReport | Observation) | Formal record of assessment
| C | 0..* | Reference(ClinicalImpression | DiagnosticReport | Observation) | Formal record of assessment
| |
 type | | | | | | 0..1 | CodeableConcept | Kind of staging
Binding: todo (example): Codes describing the kind of condition staging (e.g. clinical or pathological).
| |
| evidence | ΣC | 0..* | BackboneElement | Supporting evidence
con-2: evidence SHALL have code or details
| C | 0..* | BackboneElement | Supporting evidence
| - Elements differ in definition: 'Supporting Evidence / manifestations that are the basis on which this condition is suspected or confirmed.' vs 'Supporting evidence / manifestations that are the basis of the Condition's verification status, such as evidence that confirmed or refuted the condition.'
|
| id | | 0..1 | id | xml:id (or equivalent in JSON) | | 0..1 | string | Unique id for inter-element referencing | - Elements differ in short: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
- Elements differ in definition: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
|
| extension | | 0..* | Extension | Additional Content defined by implementations
| | 0..* | Extension | Additional content defined by implementations
| - Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.'
|
| modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored
| ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized
| - Elements differ in short: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized'
- Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order to make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
|
| code | ΣC | 0..1 | CodeableConcept | Manifestation/symptom
Binding: todo (example): Codes that describe the manifestation or symptoms of a condition.
| ΣC | 0..* | CodeableConcept | Manifestation/symptom
Binding: todo (example): Codes that describe the manifestation or symptoms of a condition.
| - Element maximum cardinalities differ: '1' vs '2147483647'
|
| detail | ΣC | 0..* | Reference(Resource) | Supporting information found elsewhere
| ΣC | 0..* | Reference(Resource) | Supporting information found elsewhere
| |
| bodySite | Σ | 0..* | CodeableConcept | Anatomical location, if relevant
Binding: todo (example): Codes describing anatomical locations. May include laterality.
| Σ | 0..* | CodeableConcept | Anatomical location, if relevant
Binding: todo (example): Codes describing anatomical locations. May include laterality.
| - Elements differ in comments: 'May be a summary code, or a reference to a very precise definition of the location, or both.' vs 'Only used if not implicit in code found in Condition.code. If the use case requires attributes from the BodySite resource (e.g. to identify and track separately) then use the standard extension [bodySite]. May be a summary code, or a reference to a very precise definition of the location, or both.'
|
| notes | Σ | 0..1 | string | Additional information about the Condition | | | | | |
| subject | | | | | SΣ | 1..1 | Reference(http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient) | (USCDI) Who has the condition? | |
| recordedDate | | | | | SΣ | 0..1 | dateTime | (USCDI) Date record was first recorded | |
| recorder | | | | | Σ | 0..1 | Reference(Practitioner | PractitionerRole | Patient | RelatedPerson) | Who recorded the condition | |
| note | | | | | | 0..* | Annotation | Additional information about the Condition
| |
Documentation for this format |