Significant health events and conditions for a person related to the patient relevant in the context of care for the patient.
| CareConnect-FamilyMemberHistory-1 (FamilyMemberHistory) | I | FamilyMemberHistory | There are no (further) constraints on this element Element idFamilyMemberHistory Information about patient's relatives, relevant for patient DefinitionSignificant health events and conditions for a person related to the patient relevant in the context of care for the patient.
| |
| id | Σ | 0..1 | id | There are no (further) constraints on this element Element idFamilyMemberHistory.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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 | There are no (further) constraints on this element Element idFamilyMemberHistory.meta Metadata about the resource DefinitionThe 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. |
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idFamilyMemberHistory.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. |
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idFamilyMemberHistory.language Language of the resource content DefinitionThe base language in which the resource is written. 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). A human language. Common Languages (extensible) | |
| text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idFamilyMemberHistory.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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. 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 in formation is added later.
|
| contained | 0..* | Resource | There are no (further) constraints on this element Element idFamilyMemberHistory.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. 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.
| |
| extension | 0..* | Extension | Element idFamilyMemberHistory.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Mappings
| |
| recorder | I | 0..1 | Extension(Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1)) | Element idFamilyMemberHistory.extension:recorder Who recorded the event Alternate namesextensions, user content DefinitionWho recorded the event. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1)) Extension URLhttps://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-CareConnect-Recorder-1 Constraints
|
| encounter | I | 0..1 | Extension(Reference(Encounter)) | Element idFamilyMemberHistory.extension:encounter Associated Encounter Alternate namesextensions, user content DefinitionThis encounter occurs within the scope of the referenced encounter. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Reference(Encounter)) Extension URLhttp://hl7.org/fhir/StructureDefinition/encounter-associatedEncounter Constraints
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.extension:encounter.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.extension:encounter.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idFamilyMemberHistory.extension:encounter.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/StructureDefinition/encounter-associatedEncounter
| |
| valueReference | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idFamilyMemberHistory.extension:encounter.valueReference:valueReference Value of extension DefinitionValue of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).
| |
| modifierExtension | ?! | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier External Id(s) for this record DefinitionThis records identifiers associated with this family member history record 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). Need to allow connection to a wider workflow.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.use usual | official | temp | secondary (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Mappings
|
| type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Mappings
|
| system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. General http://www.acme.com/identifiers/patient Mappings
|
| value | Σ | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. General 123456 Mappings
|
| period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
|
| assigner | Σ | 0..1 | Reference(CareConnect-Organization-1) | Element idFamilyMemberHistory.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(CareConnect-Organization-1) Mappings
|
| definition | Σ | 0..* | Reference(PlanDefinition | Questionnaire) | There are no (further) constraints on this element Element idFamilyMemberHistory.definition Instantiates protocol or definition DefinitionA protocol or questionnaire that was adhered to in whole or in part by this event. Reference(PlanDefinition | Questionnaire) Mappings
|
| status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idFamilyMemberHistory.status partial | completed | entered-in-error | health-unknown DefinitionA code specifying the status of the record of the family history of a specific family member. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. A code that identifies the status of the family history record. FamilyHistoryStatus (required)Mappings
|
| notDone | Σ ?! | 0..1 | boolean | There are no (further) constraints on this element Element idFamilyMemberHistory.notDone The taking of a family member's history did not occur DefinitionIf true, indicates the taking of an individual family member's history did not occur. The notDone element should not be used to document negated conditions, such as a family member that did not have a condition. Creating a FamilyMemberHistory where notDone is true is intended for situations where there's a need for a specific statement in the record about something not being done. If the need is merely to indicate that a request wasn't fulfilled, that should be handled using Task. This element is labeled as a modifier because it marks the family member history as a family member history that did not occur. The more attributes are populated, the more constrained the negated statement is. This notDone element is being evaluated and will likely be removed in a subsequent release. false
|
| notDoneReason | Σ I | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idFamilyMemberHistory.notDoneReason subject-unknown | withheld | unable-to-obtain | deferred DefinitionDescribes why the family member's history is absent. This is a separate element to allow it to have a distinct binding from reasonCode. This notDoneReason element is being evaluated and will likely be replaced in a subsequent release (e.g. dataAbsentReason). Codes describing the reason why a family member history was not done. FamilyHistoryNotDoneReason (example)Mappings
|
| patient | Σ | 1..1 | Reference(CareConnect-Patient-1) | Element idFamilyMemberHistory.patient Patient history is about Alternate namesProband DefinitionThe person who this history concerns. Reference(CareConnect-Patient-1) Mappings
|
| date | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idFamilyMemberHistory.date When history was captured/updated DefinitionThe date (and possibly time) when the family member history was taken. Allows determination of how current the summary is. This should be captured even if the same as the date on the List aggregating the full family history.
|
| name | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.name The family member described DefinitionThis will either be a name or a description; e.g. "Aunt Susan", "my cousin with the red hair". Allows greater ease in ensuring the same person is being talked about.
|
| relationship | Σ | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship Relationship to the subject DefinitionThe type of relationship this person has to the patient (father, mother, brother etc.). The nature of the relationship between the patient and the related person being described in the family member history. FamilyMember (example)Mappings
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| coding | Σ | 0..* | Coding | Element idFamilyMemberHistory.relationship.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Unordered, Open, by system(Value) Mappings
|
| snomedCT | Σ | 0..1 | Coding | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | Element idFamilyMemberHistory.relationship.coding:snomedCT.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| snomedCTDescriptionID | I | 0..1 | Extension(Complex) | Element idFamilyMemberHistory.relationship.coding:snomedCT.extension:snomedCTDescriptionID The SNOMED CT Description ID for the display Alternate namesextensions, user content DefinitionThe SNOMED CT Description ID for the display. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-coding-sctdescid Constraints
|
| system | Σ | 1..1 | uriFixed Value | Element idFamilyMemberHistory.relationship.coding:snomedCT.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. http://snomed.info/sct
|
| version | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
| code | Σ | 1..1 | code | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system.
|
| display | Σ | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
| userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| gender | Σ | 0..1 | codeBinding | Element idFamilyMemberHistory.gender male | female | other | unknown DefinitionAdministrative Gender - the gender that the relative is considered to have for administration and record keeping purposes. Not all relationship codes imply gender and the relative's gender can be relevant for risk assessments. The gender of a person used for administrative purposes. Administrative Gender (required) |
| born[x] | I | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.born[x] (approximate) date of birth DefinitionThe actual or approximate date of birth of the relative. Allows calculation of the relative's age.
| |
| bornPeriod | Period | There are no (further) constraints on this element Data type | ||
| bornDate | date | There are no (further) constraints on this element Data type | ||
| bornString | string | There are no (further) constraints on this element Data type | ||
| age[x] | Σ I | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.age[x] (approximate) age DefinitionThe age of the relative at the time the family member history is recorded. While age can be calculated from date of birth, sometimes recording age directly is more natureal for clinicians. use estimatedAge to indicate whether the age is actual or not.
| |
| ageAge | Age | There are no (further) constraints on this element Data type | ||
| ageRange | Range | There are no (further) constraints on this element Data type | ||
| ageString | string | There are no (further) constraints on this element Data type | ||
| estimatedAge | Σ ?! I | 0..1 | boolean | There are no (further) constraints on this element Element idFamilyMemberHistory.estimatedAge Age is estimated? DefinitionIf true, indicates that the age value specified is an estimated value. Clinicians often prefer to specify an estimaged age rather than an age range. This element is labeled as a modifier because the fact tha age is estimated can/should change the results of any algorithm that calculates based on the specified age. It is unknown whether the age is an estimate or not |
| deceased[x] | Σ | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.deceased[x] Dead? How old/when? DefinitionDeceased flag or the actual or approximate age of the relative at the time of death for the family member history record.
| |
| deceasedBoolean | boolean | There are no (further) constraints on this element Data type | ||
| deceasedAge | Age | There are no (further) constraints on this element Data type | ||
| deceasedRange | Range | There are no (further) constraints on this element Data type | ||
| deceasedDate | date | There are no (further) constraints on this element Data type | ||
| deceasedString | string | There are no (further) constraints on this element Data type | ||
| reasonCode | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idFamilyMemberHistory.reasonCode Why was family member history performed? DefinitionDescribes why the family member history occurred in coded or textual form. Textual reasons can be caprued using reasonCode.text. Codes indicating why the family member history was done. SNOMED CT Clinical Findings (example)Mappings
|
| reasonReference | Σ | 0..* | Reference(QuestionnaireResponse | CareConnect-Observation-1 | CareConnect-Condition-1 | CareConnect-AllergyIntolerance-1) | Element idFamilyMemberHistory.reasonReference Why was family member history performed? DefinitionIndicates a Condition, Observation, AllergyIntolerance, or QuestionnaireResponse that justifies this family member history event. Reference(QuestionnaireResponse | CareConnect-Observation-1 | CareConnect-Condition-1 | CareConnect-AllergyIntolerance-1) Mappings
|
| note | 0..* | Annotation | There are no (further) constraints on this element Element idFamilyMemberHistory.note General note about related person DefinitionThis property allows a non condition-specific note to the made about the related person. Ideally, the note would be in the condition property, but this is not always possible.
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.note.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.note.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| author[x] | Σ | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.note.author[x] Individual responsible for the annotation DefinitionThe individual responsible for making the annotation.
| |
| authorString | string | Data type | ||
| authorReference | Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1 | CareConnect-RelatedPerson-1) | Data type Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1 | CareConnect-RelatedPerson-1) | ||
| time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idFamilyMemberHistory.note.time When the annotation was made DefinitionIndicates when this particular annotation was made.
|
| text | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.note.text The annotation - text content DefinitionThe text of the annotation.
| |
| condition | 0..* | BackboneElement | There are no (further) constraints on this element Element idFamilyMemberHistory.condition Condition that the related person had DefinitionThe significant Conditions (or condition) that the family member had. This is a repeating section to allow a system to represent more than one condition per resource, though there is nothing stopping multiple resources - one per condition. If none of the conditions listed have an outcome of "death" specified, that indicates that none of the specified conditions are known to have been the primary cause of death.
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
| |
| modifierExtension | Σ ?! | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| code | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code Condition suffered by relation DefinitionThe actual condition specified. Could be a coded condition (like MI or Diabetes) or a less specific string like 'cancer' depending on how much is known about the condition and the capabilities of the creating system. Identification of the Condition or diagnosis. Condition/Problem/Diagnosis Codes (example)Mappings
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| coding | Σ | 0..* | Coding | Element idFamilyMemberHistory.condition.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Unordered, Open, by system(Value) Mappings
|
| snomedCT | Σ | 0..1 | Coding | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | Element idFamilyMemberHistory.condition.code.coding:snomedCT.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| snomedCTDescriptionID | I | 0..1 | Extension(Complex) | Element idFamilyMemberHistory.condition.code.coding:snomedCT.extension:snomedCTDescriptionID The SNOMED CT Description ID for the display Alternate namesextensions, user content DefinitionThe SNOMED CT Description ID for the display. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-coding-sctdescid Constraints
|
| system | Σ | 1..1 | uriFixed Value | Element idFamilyMemberHistory.condition.code.coding:snomedCT.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. http://snomed.info/sct
|
| version | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
| code | Σ | 1..1 | code | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system.
|
| display | Σ | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
| userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| outcome | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome deceased | permanent disability | etc. DefinitionIndicates what happened as a result of this condition. If the condition resulted in death, deceased date is captured on the relation. The result of the condition for the patient; e.g. death, permanent disability, temporary disability, etc. Condition Outcome Codes (example)Mappings
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| coding | Σ | 0..* | Coding | Element idFamilyMemberHistory.condition.outcome.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Unordered, Open, by system(Value) Mappings
|
| snomedCT | Σ | 0..1 | Coding | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| snomedCTDescriptionID | I | 0..1 | Extension(Complex) | Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.extension:snomedCTDescriptionID The SNOMED CT Description ID for the display Alternate namesextensions, user content DefinitionThe SNOMED CT Description ID for the display. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-coding-sctdescid Constraints
|
| system | Σ | 1..1 | uriFixed Value | Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. http://snomed.info/sct
|
| version | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
| code | Σ | 1..1 | code | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system.
|
| display | Σ | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
| userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| onset[x] | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.onset[x] When condition first manifested DefinitionEither the age of onset, range of approximate age or descriptive string can be recorded. For conditions with multiple occurrences, this describes the first known occurrence. Age of onset of a condition in relatives is predictive of risk for the patient.
| ||
| onsetAge | Age | There are no (further) constraints on this element Data type | ||
| onsetRange | Range | There are no (further) constraints on this element Data type | ||
| onsetPeriod | Period | There are no (further) constraints on this element Data type | ||
| onsetString | string | There are no (further) constraints on this element Data type | ||
| note | 0..* | Annotation | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note Extra information about condition DefinitionAn area where general notes can be placed about this specific condition.
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| author[x] | Σ | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note.author[x] Individual responsible for the annotation DefinitionThe individual responsible for making the annotation.
| |
| authorString | string | Data type | ||
| authorReference | Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1 | CareConnect-RelatedPerson-1) | Data type Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1 | CareConnect-RelatedPerson-1) | ||
| time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note.time When the annotation was made DefinitionIndicates when this particular annotation was made.
|
| text | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note.text The annotation - text content DefinitionThe text of the annotation.
|
| CareConnect-FamilyMemberHistory-1 (FamilyMemberHistory) | I | FamilyMemberHistory | There are no (further) constraints on this element Element idFamilyMemberHistory Information about patient's relatives, relevant for patient DefinitionSignificant health events and conditions for a person related to the patient relevant in the context of care for the patient.
| |
| id | Σ | 0..1 | id | There are no (further) constraints on this element Element idFamilyMemberHistory.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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 | There are no (further) constraints on this element Element idFamilyMemberHistory.meta Metadata about the resource DefinitionThe 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. |
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idFamilyMemberHistory.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. |
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idFamilyMemberHistory.language Language of the resource content DefinitionThe base language in which the resource is written. 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). A human language. Common Languages (extensible) | |
| text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idFamilyMemberHistory.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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. 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 in formation is added later.
|
| contained | 0..* | Resource | There are no (further) constraints on this element Element idFamilyMemberHistory.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. 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.
| |
| extension | 0..* | Extension | Element idFamilyMemberHistory.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Mappings
| |
| recorder | I | 0..1 | Extension(Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1)) | Element idFamilyMemberHistory.extension:recorder Who recorded the event Alternate namesextensions, user content DefinitionWho recorded the event. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1)) Extension URLhttps://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-CareConnect-Recorder-1 Constraints
|
| encounter | I | 0..1 | Extension(Reference(Encounter)) | Element idFamilyMemberHistory.extension:encounter Associated Encounter Alternate namesextensions, user content DefinitionThis encounter occurs within the scope of the referenced encounter. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Reference(Encounter)) Extension URLhttp://hl7.org/fhir/StructureDefinition/encounter-associatedEncounter Constraints
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.extension:encounter.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.extension:encounter.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idFamilyMemberHistory.extension:encounter.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/StructureDefinition/encounter-associatedEncounter
| |
| valueReference | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idFamilyMemberHistory.extension:encounter.valueReference:valueReference Value of extension DefinitionValue of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).
| |
| modifierExtension | ?! | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier External Id(s) for this record DefinitionThis records identifiers associated with this family member history record 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). Need to allow connection to a wider workflow.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.use usual | official | temp | secondary (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Mappings
|
| type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Mappings
|
| system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. General http://www.acme.com/identifiers/patient Mappings
|
| value | Σ | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. General 123456 Mappings
|
| period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
|
| assigner | Σ | 0..1 | Reference(CareConnect-Organization-1) | Element idFamilyMemberHistory.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(CareConnect-Organization-1) Mappings
|
| definition | Σ | 0..* | Reference(PlanDefinition | Questionnaire) | There are no (further) constraints on this element Element idFamilyMemberHistory.definition Instantiates protocol or definition DefinitionA protocol or questionnaire that was adhered to in whole or in part by this event. Reference(PlanDefinition | Questionnaire) Mappings
|
| status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idFamilyMemberHistory.status partial | completed | entered-in-error | health-unknown DefinitionA code specifying the status of the record of the family history of a specific family member. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. A code that identifies the status of the family history record. FamilyHistoryStatus (required)Mappings
|
| notDone | Σ ?! | 0..1 | boolean | There are no (further) constraints on this element Element idFamilyMemberHistory.notDone The taking of a family member's history did not occur DefinitionIf true, indicates the taking of an individual family member's history did not occur. The notDone element should not be used to document negated conditions, such as a family member that did not have a condition. Creating a FamilyMemberHistory where notDone is true is intended for situations where there's a need for a specific statement in the record about something not being done. If the need is merely to indicate that a request wasn't fulfilled, that should be handled using Task. This element is labeled as a modifier because it marks the family member history as a family member history that did not occur. The more attributes are populated, the more constrained the negated statement is. This notDone element is being evaluated and will likely be removed in a subsequent release. false
|
| notDoneReason | Σ I | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idFamilyMemberHistory.notDoneReason subject-unknown | withheld | unable-to-obtain | deferred DefinitionDescribes why the family member's history is absent. This is a separate element to allow it to have a distinct binding from reasonCode. This notDoneReason element is being evaluated and will likely be replaced in a subsequent release (e.g. dataAbsentReason). Codes describing the reason why a family member history was not done. FamilyHistoryNotDoneReason (example)Mappings
|
| patient | Σ | 1..1 | Reference(CareConnect-Patient-1) | Element idFamilyMemberHistory.patient Patient history is about Alternate namesProband DefinitionThe person who this history concerns. Reference(CareConnect-Patient-1) Mappings
|
| date | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idFamilyMemberHistory.date When history was captured/updated DefinitionThe date (and possibly time) when the family member history was taken. Allows determination of how current the summary is. This should be captured even if the same as the date on the List aggregating the full family history.
|
| name | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.name The family member described DefinitionThis will either be a name or a description; e.g. "Aunt Susan", "my cousin with the red hair". Allows greater ease in ensuring the same person is being talked about.
|
| relationship | Σ | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship Relationship to the subject DefinitionThe type of relationship this person has to the patient (father, mother, brother etc.). The nature of the relationship between the patient and the related person being described in the family member history. FamilyMember (example)Mappings
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| coding | Σ | 0..* | Coding | Element idFamilyMemberHistory.relationship.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Unordered, Open, by system(Value) Mappings
|
| snomedCT | Σ | 0..1 | Coding | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | Element idFamilyMemberHistory.relationship.coding:snomedCT.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| snomedCTDescriptionID | I | 0..1 | Extension(Complex) | Element idFamilyMemberHistory.relationship.coding:snomedCT.extension:snomedCTDescriptionID The SNOMED CT Description ID for the display Alternate namesextensions, user content DefinitionThe SNOMED CT Description ID for the display. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-coding-sctdescid Constraints
|
| system | Σ | 1..1 | uriFixed Value | Element idFamilyMemberHistory.relationship.coding:snomedCT.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. http://snomed.info/sct
|
| version | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
| code | Σ | 1..1 | code | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system.
|
| display | Σ | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
| userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| gender | Σ | 0..1 | codeBinding | Element idFamilyMemberHistory.gender male | female | other | unknown DefinitionAdministrative Gender - the gender that the relative is considered to have for administration and record keeping purposes. Not all relationship codes imply gender and the relative's gender can be relevant for risk assessments. The gender of a person used for administrative purposes. Administrative Gender (required) |
| born[x] | I | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.born[x] (approximate) date of birth DefinitionThe actual or approximate date of birth of the relative. Allows calculation of the relative's age.
| |
| bornPeriod | Period | There are no (further) constraints on this element Data type | ||
| bornDate | date | There are no (further) constraints on this element Data type | ||
| bornString | string | There are no (further) constraints on this element Data type | ||
| age[x] | Σ I | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.age[x] (approximate) age DefinitionThe age of the relative at the time the family member history is recorded. While age can be calculated from date of birth, sometimes recording age directly is more natureal for clinicians. use estimatedAge to indicate whether the age is actual or not.
| |
| ageAge | Age | There are no (further) constraints on this element Data type | ||
| ageRange | Range | There are no (further) constraints on this element Data type | ||
| ageString | string | There are no (further) constraints on this element Data type | ||
| estimatedAge | Σ ?! I | 0..1 | boolean | There are no (further) constraints on this element Element idFamilyMemberHistory.estimatedAge Age is estimated? DefinitionIf true, indicates that the age value specified is an estimated value. Clinicians often prefer to specify an estimaged age rather than an age range. This element is labeled as a modifier because the fact tha age is estimated can/should change the results of any algorithm that calculates based on the specified age. It is unknown whether the age is an estimate or not |
| deceased[x] | Σ | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.deceased[x] Dead? How old/when? DefinitionDeceased flag or the actual or approximate age of the relative at the time of death for the family member history record.
| |
| deceasedBoolean | boolean | There are no (further) constraints on this element Data type | ||
| deceasedAge | Age | There are no (further) constraints on this element Data type | ||
| deceasedRange | Range | There are no (further) constraints on this element Data type | ||
| deceasedDate | date | There are no (further) constraints on this element Data type | ||
| deceasedString | string | There are no (further) constraints on this element Data type | ||
| reasonCode | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idFamilyMemberHistory.reasonCode Why was family member history performed? DefinitionDescribes why the family member history occurred in coded or textual form. Textual reasons can be caprued using reasonCode.text. Codes indicating why the family member history was done. SNOMED CT Clinical Findings (example)Mappings
|
| reasonReference | Σ | 0..* | Reference(QuestionnaireResponse | CareConnect-Observation-1 | CareConnect-Condition-1 | CareConnect-AllergyIntolerance-1) | Element idFamilyMemberHistory.reasonReference Why was family member history performed? DefinitionIndicates a Condition, Observation, AllergyIntolerance, or QuestionnaireResponse that justifies this family member history event. Reference(QuestionnaireResponse | CareConnect-Observation-1 | CareConnect-Condition-1 | CareConnect-AllergyIntolerance-1) Mappings
|
| note | 0..* | Annotation | There are no (further) constraints on this element Element idFamilyMemberHistory.note General note about related person DefinitionThis property allows a non condition-specific note to the made about the related person. Ideally, the note would be in the condition property, but this is not always possible.
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.note.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.note.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| author[x] | Σ | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.note.author[x] Individual responsible for the annotation DefinitionThe individual responsible for making the annotation.
| |
| authorString | string | Data type | ||
| authorReference | Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1 | CareConnect-RelatedPerson-1) | Data type Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1 | CareConnect-RelatedPerson-1) | ||
| time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idFamilyMemberHistory.note.time When the annotation was made DefinitionIndicates when this particular annotation was made.
|
| text | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.note.text The annotation - text content DefinitionThe text of the annotation.
| |
| condition | 0..* | BackboneElement | There are no (further) constraints on this element Element idFamilyMemberHistory.condition Condition that the related person had DefinitionThe significant Conditions (or condition) that the family member had. This is a repeating section to allow a system to represent more than one condition per resource, though there is nothing stopping multiple resources - one per condition. If none of the conditions listed have an outcome of "death" specified, that indicates that none of the specified conditions are known to have been the primary cause of death.
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
| |
| modifierExtension | Σ ?! | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| code | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code Condition suffered by relation DefinitionThe actual condition specified. Could be a coded condition (like MI or Diabetes) or a less specific string like 'cancer' depending on how much is known about the condition and the capabilities of the creating system. Identification of the Condition or diagnosis. Condition/Problem/Diagnosis Codes (example)Mappings
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| coding | Σ | 0..* | Coding | Element idFamilyMemberHistory.condition.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Unordered, Open, by system(Value) Mappings
|
| snomedCT | Σ | 0..1 | Coding | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | Element idFamilyMemberHistory.condition.code.coding:snomedCT.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| snomedCTDescriptionID | I | 0..1 | Extension(Complex) | Element idFamilyMemberHistory.condition.code.coding:snomedCT.extension:snomedCTDescriptionID The SNOMED CT Description ID for the display Alternate namesextensions, user content DefinitionThe SNOMED CT Description ID for the display. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-coding-sctdescid Constraints
|
| system | Σ | 1..1 | uriFixed Value | Element idFamilyMemberHistory.condition.code.coding:snomedCT.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. http://snomed.info/sct
|
| version | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
| code | Σ | 1..1 | code | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system.
|
| display | Σ | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
| userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| outcome | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome deceased | permanent disability | etc. DefinitionIndicates what happened as a result of this condition. If the condition resulted in death, deceased date is captured on the relation. The result of the condition for the patient; e.g. death, permanent disability, temporary disability, etc. Condition Outcome Codes (example)Mappings
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| coding | Σ | 0..* | Coding | Element idFamilyMemberHistory.condition.outcome.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Unordered, Open, by system(Value) Mappings
|
| snomedCT | Σ | 0..1 | Coding | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| snomedCTDescriptionID | I | 0..1 | Extension(Complex) | Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.extension:snomedCTDescriptionID The SNOMED CT Description ID for the display Alternate namesextensions, user content DefinitionThe SNOMED CT Description ID for the display. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-coding-sctdescid Constraints
|
| system | Σ | 1..1 | uriFixed Value | Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. http://snomed.info/sct
|
| version | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
| code | Σ | 1..1 | code | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system.
|
| display | Σ | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
| userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| onset[x] | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.onset[x] When condition first manifested DefinitionEither the age of onset, range of approximate age or descriptive string can be recorded. For conditions with multiple occurrences, this describes the first known occurrence. Age of onset of a condition in relatives is predictive of risk for the patient.
| ||
| onsetAge | Age | There are no (further) constraints on this element Data type | ||
| onsetRange | Range | There are no (further) constraints on this element Data type | ||
| onsetPeriod | Period | There are no (further) constraints on this element Data type | ||
| onsetString | string | There are no (further) constraints on this element Data type | ||
| note | 0..* | Annotation | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note Extra information about condition DefinitionAn area where general notes can be placed about this specific condition.
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| author[x] | Σ | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note.author[x] Individual responsible for the annotation DefinitionThe individual responsible for making the annotation.
| |
| authorString | string | Data type | ||
| authorReference | Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1 | CareConnect-RelatedPerson-1) | Data type Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1 | CareConnect-RelatedPerson-1) | ||
| time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note.time When the annotation was made DefinitionIndicates when this particular annotation was made.
|
| text | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note.text The annotation - text content DefinitionThe text of the annotation.
|
| CareConnect-FamilyMemberHistory-1 (FamilyMemberHistory) | I | FamilyMemberHistory | There are no (further) constraints on this element Element idFamilyMemberHistory Information about patient's relatives, relevant for patient DefinitionSignificant health events and conditions for a person related to the patient relevant in the context of care for the patient.
| |
| id | Σ | 0..1 | id | There are no (further) constraints on this element Element idFamilyMemberHistory.id Logical id of this artifact DefinitionThe logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes. 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 | There are no (further) constraints on this element Element idFamilyMemberHistory.meta Metadata about the resource DefinitionThe 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. |
| implicitRules | Σ ?! | 0..1 | uri | There are no (further) constraints on this element Element idFamilyMemberHistory.implicitRules A set of rules under which this content was created DefinitionA reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. 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. This element is labelled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies it's meaning or interpretation. |
| language | 0..1 | codeBinding | There are no (further) constraints on this element Element idFamilyMemberHistory.language Language of the resource content DefinitionThe base language in which the resource is written. 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). A human language. Common Languages (extensible) | |
| text | I | 0..1 | Narrative | There are no (further) constraints on this element Element idFamilyMemberHistory.text Text summary of the resource, for human interpretation Alternate namesnarrative, html, xhtml, display DefinitionA 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. 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 in formation is added later.
|
| contained | 0..* | Resource | There are no (further) constraints on this element Element idFamilyMemberHistory.contained Contained, inline Resources Alternate namesinline resources, anonymous resources, contained resources DefinitionThese resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, and nor can they have their own independent transaction scope. 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.
| |
| extension | 0..* | Extension | Element idFamilyMemberHistory.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Mappings
| |
| recorder | I | 0..1 | Extension(Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1)) | Element idFamilyMemberHistory.extension:recorder Who recorded the event Alternate namesextensions, user content DefinitionWho recorded the event. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1)) Extension URLhttps://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-CareConnect-Recorder-1 Constraints
|
| encounter | I | 0..1 | Extension(Reference(Encounter)) | Element idFamilyMemberHistory.extension:encounter Associated Encounter Alternate namesextensions, user content DefinitionThis encounter occurs within the scope of the referenced encounter. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Reference(Encounter)) Extension URLhttp://hl7.org/fhir/StructureDefinition/encounter-associatedEncounter Constraints
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.extension:encounter.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.extension:encounter.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| url | 1..1 | uriFixed Value | There are no (further) constraints on this element Element idFamilyMemberHistory.extension:encounter.url identifies the meaning of the extension DefinitionSource of the definition for the extension code - a logical name or a URL. The definition may point directly to a computable or human-readable definition of the extensibility codes, or it may be a logical URI as declared in some other specification. The definition SHALL be a URI for the Structure Definition defining the extension. http://hl7.org/fhir/StructureDefinition/encounter-associatedEncounter
| |
| valueReference | 0..1 | Reference(Encounter) | There are no (further) constraints on this element Element idFamilyMemberHistory.extension:encounter.valueReference:valueReference Value of extension DefinitionValue of extension - may be a resource or one of a constrained set of the data types (see Extensibility in the spec for list).
| |
| modifierExtension | ?! | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| identifier | Σ | 0..* | Identifier | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier External Id(s) for this record DefinitionThis records identifiers associated with this family member history record 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). Need to allow connection to a wider workflow.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| use | Σ ?! | 0..1 | codeBinding | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.use usual | official | temp | secondary (If known) DefinitionThe purpose of this identifier. Allows the appropriate identifier for a particular context of use to be selected from among a set of identifiers. This is labeled as "Is Modifier" because applications should not mistake a temporary id for a permanent one. Applications can assume that an identifier is permanent unless it explicitly says that it is temporary. Identifies the purpose for this identifier, if known . IdentifierUse (required)Mappings
|
| type | Σ | 0..1 | CodeableConceptBinding | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.type Description of identifier DefinitionA coded type for the identifier that can be used to determine which identifier to use for a specific purpose. Allows users to make use of identifiers when the identifier system is not known. This element deals only with general categories of identifiers. It SHOULD not be used for codes that correspond 1..1 with the Identifier.system. Some identifiers may fall into multiple categories due to common usage. Where the system is known, a type is unnecessary because the type is always part of the system definition. However systems often need to handle identifiers where the system is not known. There is not a 1:1 relationship between type and system, since many different systems have the same type. A coded type for an identifier that can be used to determine which identifier to use for a specific purpose. Identifier Type Codes (extensible)Mappings
|
| system | Σ | 1..1 | uri | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.system The namespace for the identifier value DefinitionEstablishes the namespace for the value - that is, a URL that describes a set values that are unique. There are many sets of identifiers. To perform matching of two identifiers, we need to know what set we're dealing with. The system identifies a particular set of unique identifiers. General http://www.acme.com/identifiers/patient Mappings
|
| value | Σ | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.value The value that is unique DefinitionThe portion of the identifier typically relevant to the user and which is unique within the context of the system. If the value is a full URI, then the system SHALL be urn:ietf:rfc:3986. The value's primary purpose is computational mapping. As a result, it may be normalized for comparison purposes (e.g. removing non-significant whitespace, dashes, etc.) A value formatted for human display can be conveyed using the Rendered Value extension. General 123456 Mappings
|
| period | Σ | 0..1 | Period | There are no (further) constraints on this element Element idFamilyMemberHistory.identifier.period Time period when id is/was valid for use DefinitionTime period during which identifier is/was valid for use.
|
| assigner | Σ | 0..1 | Reference(CareConnect-Organization-1) | Element idFamilyMemberHistory.identifier.assigner Organization that issued id (may be just text) DefinitionOrganization that issued/manages the identifier. The Identifier.assigner may omit the .reference element and only contain a .display element reflecting the name or other textual information about the assigning organization. Reference(CareConnect-Organization-1) Mappings
|
| definition | Σ | 0..* | Reference(PlanDefinition | Questionnaire) | There are no (further) constraints on this element Element idFamilyMemberHistory.definition Instantiates protocol or definition DefinitionA protocol or questionnaire that was adhered to in whole or in part by this event. Reference(PlanDefinition | Questionnaire) Mappings
|
| status | Σ ?! | 1..1 | codeBinding | There are no (further) constraints on this element Element idFamilyMemberHistory.status partial | completed | entered-in-error | health-unknown DefinitionA code specifying the status of the record of the family history of a specific family member. This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid. A code that identifies the status of the family history record. FamilyHistoryStatus (required)Mappings
|
| notDone | Σ ?! | 0..1 | boolean | There are no (further) constraints on this element Element idFamilyMemberHistory.notDone The taking of a family member's history did not occur DefinitionIf true, indicates the taking of an individual family member's history did not occur. The notDone element should not be used to document negated conditions, such as a family member that did not have a condition. Creating a FamilyMemberHistory where notDone is true is intended for situations where there's a need for a specific statement in the record about something not being done. If the need is merely to indicate that a request wasn't fulfilled, that should be handled using Task. This element is labeled as a modifier because it marks the family member history as a family member history that did not occur. The more attributes are populated, the more constrained the negated statement is. This notDone element is being evaluated and will likely be removed in a subsequent release. false
|
| notDoneReason | Σ I | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idFamilyMemberHistory.notDoneReason subject-unknown | withheld | unable-to-obtain | deferred DefinitionDescribes why the family member's history is absent. This is a separate element to allow it to have a distinct binding from reasonCode. This notDoneReason element is being evaluated and will likely be replaced in a subsequent release (e.g. dataAbsentReason). Codes describing the reason why a family member history was not done. FamilyHistoryNotDoneReason (example)Mappings
|
| patient | Σ | 1..1 | Reference(CareConnect-Patient-1) | Element idFamilyMemberHistory.patient Patient history is about Alternate namesProband DefinitionThe person who this history concerns. Reference(CareConnect-Patient-1) Mappings
|
| date | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idFamilyMemberHistory.date When history was captured/updated DefinitionThe date (and possibly time) when the family member history was taken. Allows determination of how current the summary is. This should be captured even if the same as the date on the List aggregating the full family history.
|
| name | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.name The family member described DefinitionThis will either be a name or a description; e.g. "Aunt Susan", "my cousin with the red hair". Allows greater ease in ensuring the same person is being talked about.
|
| relationship | Σ | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship Relationship to the subject DefinitionThe type of relationship this person has to the patient (father, mother, brother etc.). The nature of the relationship between the patient and the related person being described in the family member history. FamilyMember (example)Mappings
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| coding | Σ | 0..* | Coding | Element idFamilyMemberHistory.relationship.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Unordered, Open, by system(Value) Mappings
|
| snomedCT | Σ | 0..1 | Coding | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | Element idFamilyMemberHistory.relationship.coding:snomedCT.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| snomedCTDescriptionID | I | 0..1 | Extension(Complex) | Element idFamilyMemberHistory.relationship.coding:snomedCT.extension:snomedCTDescriptionID The SNOMED CT Description ID for the display Alternate namesextensions, user content DefinitionThe SNOMED CT Description ID for the display. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-coding-sctdescid Constraints
|
| system | Σ | 1..1 | uriFixed Value | Element idFamilyMemberHistory.relationship.coding:snomedCT.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. http://snomed.info/sct
|
| version | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
| code | Σ | 1..1 | code | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system.
|
| display | Σ | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
| userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.coding:snomedCT.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.relationship.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| gender | Σ | 0..1 | codeBinding | Element idFamilyMemberHistory.gender male | female | other | unknown DefinitionAdministrative Gender - the gender that the relative is considered to have for administration and record keeping purposes. Not all relationship codes imply gender and the relative's gender can be relevant for risk assessments. The gender of a person used for administrative purposes. Administrative Gender (required) |
| born[x] | I | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.born[x] (approximate) date of birth DefinitionThe actual or approximate date of birth of the relative. Allows calculation of the relative's age.
| |
| bornPeriod | Period | There are no (further) constraints on this element Data type | ||
| bornDate | date | There are no (further) constraints on this element Data type | ||
| bornString | string | There are no (further) constraints on this element Data type | ||
| age[x] | Σ I | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.age[x] (approximate) age DefinitionThe age of the relative at the time the family member history is recorded. While age can be calculated from date of birth, sometimes recording age directly is more natureal for clinicians. use estimatedAge to indicate whether the age is actual or not.
| |
| ageAge | Age | There are no (further) constraints on this element Data type | ||
| ageRange | Range | There are no (further) constraints on this element Data type | ||
| ageString | string | There are no (further) constraints on this element Data type | ||
| estimatedAge | Σ ?! I | 0..1 | boolean | There are no (further) constraints on this element Element idFamilyMemberHistory.estimatedAge Age is estimated? DefinitionIf true, indicates that the age value specified is an estimated value. Clinicians often prefer to specify an estimaged age rather than an age range. This element is labeled as a modifier because the fact tha age is estimated can/should change the results of any algorithm that calculates based on the specified age. It is unknown whether the age is an estimate or not |
| deceased[x] | Σ | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.deceased[x] Dead? How old/when? DefinitionDeceased flag or the actual or approximate age of the relative at the time of death for the family member history record.
| |
| deceasedBoolean | boolean | There are no (further) constraints on this element Data type | ||
| deceasedAge | Age | There are no (further) constraints on this element Data type | ||
| deceasedRange | Range | There are no (further) constraints on this element Data type | ||
| deceasedDate | date | There are no (further) constraints on this element Data type | ||
| deceasedString | string | There are no (further) constraints on this element Data type | ||
| reasonCode | Σ | 0..* | CodeableConcept | There are no (further) constraints on this element Element idFamilyMemberHistory.reasonCode Why was family member history performed? DefinitionDescribes why the family member history occurred in coded or textual form. Textual reasons can be caprued using reasonCode.text. Codes indicating why the family member history was done. SNOMED CT Clinical Findings (example)Mappings
|
| reasonReference | Σ | 0..* | Reference(QuestionnaireResponse | CareConnect-Observation-1 | CareConnect-Condition-1 | CareConnect-AllergyIntolerance-1) | Element idFamilyMemberHistory.reasonReference Why was family member history performed? DefinitionIndicates a Condition, Observation, AllergyIntolerance, or QuestionnaireResponse that justifies this family member history event. Reference(QuestionnaireResponse | CareConnect-Observation-1 | CareConnect-Condition-1 | CareConnect-AllergyIntolerance-1) Mappings
|
| note | 0..* | Annotation | There are no (further) constraints on this element Element idFamilyMemberHistory.note General note about related person DefinitionThis property allows a non condition-specific note to the made about the related person. Ideally, the note would be in the condition property, but this is not always possible.
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.note.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.note.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| author[x] | Σ | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.note.author[x] Individual responsible for the annotation DefinitionThe individual responsible for making the annotation.
| |
| authorString | string | Data type | ||
| authorReference | Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1 | CareConnect-RelatedPerson-1) | Data type Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1 | CareConnect-RelatedPerson-1) | ||
| time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idFamilyMemberHistory.note.time When the annotation was made DefinitionIndicates when this particular annotation was made.
|
| text | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.note.text The annotation - text content DefinitionThe text of the annotation.
| |
| condition | 0..* | BackboneElement | There are no (further) constraints on this element Element idFamilyMemberHistory.condition Condition that the related person had DefinitionThe significant Conditions (or condition) that the family member had. This is a repeating section to allow a system to represent more than one condition per resource, though there is nothing stopping multiple resources - one per condition. If none of the conditions listed have an outcome of "death" specified, that indicates that none of the specified conditions are known to have been the primary cause of death.
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
| |
| modifierExtension | Σ ?! | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.modifierExtension Extensions that cannot be ignored Alternate namesextensions, user content, modifiers DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
|
| code | 1..1 | CodeableConcept | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code Condition suffered by relation DefinitionThe actual condition specified. Could be a coded condition (like MI or Diabetes) or a less specific string like 'cancer' depending on how much is known about the condition and the capabilities of the creating system. Identification of the Condition or diagnosis. Condition/Problem/Diagnosis Codes (example)Mappings
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| coding | Σ | 0..* | Coding | Element idFamilyMemberHistory.condition.code.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Unordered, Open, by system(Value) Mappings
|
| snomedCT | Σ | 0..1 | Coding | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | Element idFamilyMemberHistory.condition.code.coding:snomedCT.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| snomedCTDescriptionID | I | 0..1 | Extension(Complex) | Element idFamilyMemberHistory.condition.code.coding:snomedCT.extension:snomedCTDescriptionID The SNOMED CT Description ID for the display Alternate namesextensions, user content DefinitionThe SNOMED CT Description ID for the display. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-coding-sctdescid Constraints
|
| system | Σ | 1..1 | uriFixed Value | Element idFamilyMemberHistory.condition.code.coding:snomedCT.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. http://snomed.info/sct
|
| version | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
| code | Σ | 1..1 | code | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system.
|
| display | Σ | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
| userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.coding:snomedCT.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.code.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| outcome | 0..1 | CodeableConcept | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome deceased | permanent disability | etc. DefinitionIndicates what happened as a result of this condition. If the condition resulted in death, deceased date is captured on the relation. The result of the condition for the patient; e.g. death, permanent disability, temporary disability, etc. Condition Outcome Codes (example)Mappings
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| coding | Σ | 0..* | Coding | Element idFamilyMemberHistory.condition.outcome.coding Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true. Unordered, Open, by system(Value) Mappings
|
| snomedCT | Σ | 0..1 | Coding | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT Code defined by a terminology system DefinitionA reference to a code defined by a terminology system. Allows for translations and alternate encodings within a code system. Also supports communication of the same instance to systems requiring different encodings. Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
|
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| snomedCTDescriptionID | I | 0..1 | Extension(Complex) | Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.extension:snomedCTDescriptionID The SNOMED CT Description ID for the display Alternate namesextensions, user content DefinitionThe SNOMED CT Description ID for the display. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Extension(Complex) Extension URLhttps://fhir.hl7.org.uk/STU3/StructureDefinition/Extension-coding-sctdescid Constraints
|
| system | Σ | 1..1 | uriFixed Value | Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.system Identity of the terminology system DefinitionThe identification of the code system that defines the meaning of the symbol in the code. Need to be unambiguous about the source of the definition of the symbol. The URI may be an OID (urn:oid:...) or a UUID (urn:uuid:...). OIDs and UUIDs SHALL be references to the HL7 OID registry. Otherwise, the URI should come from HL7's list of FHIR defined special URIs or it should de-reference to some definition that establish the system clearly and unambiguously. http://snomed.info/sct
|
| version | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.version Version of the system - if relevant DefinitionThe version of the code system which was used when choosing this code. Note that a well-maintained code system does not need the version reported, because the meaning of codes is consistent across versions. However this cannot consistently be assured. and when the meaning is not guaranteed to be consistent, the version SHOULD be exchanged. Where the terminology does not clearly define what string should be used to identify code system versions, the recommendation is to use the date (expressed in FHIR date format) on which that version was officially published as the version date.
|
| code | Σ | 1..1 | code | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.code Symbol in syntax defined by the system DefinitionA symbol in syntax defined by the system. The symbol may be a predefined code or an expression in a syntax defined by the coding system (e.g. post-coordination). Need to refer to a particular code in the system.
|
| display | Σ | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.display Representation defined by the system DefinitionA representation of the meaning of the code in the system, following the rules of the system. Need to be able to carry a human-readable meaning of the code for readers that do not know the system.
|
| userSelected | Σ | 0..1 | boolean | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.coding:snomedCT.userSelected If this coding was chosen directly by the user DefinitionIndicates that this coding was chosen by a user directly - i.e. off a pick list of available items (codes or displays). This has been identified as a clinical safety criterium - that this exact system/code pair was chosen explicitly, rather than inferred by the system based on some rules or language processing. Amongst a set of alternatives, a directly chosen code is the most appropriate starting point for new translations. There is some ambiguity about what exactly 'directly chosen' implies, and trading partner agreement may be needed to clarify the use of this element and its consequences more completely.
|
| text | Σ | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.outcome.text Plain text representation of the concept DefinitionA human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user. The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source. Very often the text is the same as a displayName of one of the codings.
|
| onset[x] | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.onset[x] When condition first manifested DefinitionEither the age of onset, range of approximate age or descriptive string can be recorded. For conditions with multiple occurrences, this describes the first known occurrence. Age of onset of a condition in relatives is predictive of risk for the patient.
| ||
| onsetAge | Age | There are no (further) constraints on this element Data type | ||
| onsetRange | Range | There are no (further) constraints on this element Data type | ||
| onsetPeriod | Period | There are no (further) constraints on this element Data type | ||
| onsetString | string | There are no (further) constraints on this element Data type | ||
| note | 0..* | Annotation | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note Extra information about condition DefinitionAn area where general notes can be placed about this specific condition.
| |
| id | 0..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note.id xml:id (or equivalent in JSON) Definitionunique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
| |
| extension | 0..* | Extension | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note.extension Additional Content defined by implementations Alternate namesextensions, user content DefinitionMay 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. There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone. Unordered, Open, by url(Value) Extensions are always sliced by (at least) url Mappings
| |
| author[x] | Σ | 0..1 | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note.author[x] Individual responsible for the annotation DefinitionThe individual responsible for making the annotation.
| |
| authorString | string | Data type | ||
| authorReference | Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1 | CareConnect-RelatedPerson-1) | Data type Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1 | CareConnect-RelatedPerson-1) | ||
| time | Σ | 0..1 | dateTime | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note.time When the annotation was made DefinitionIndicates when this particular annotation was made.
|
| text | 1..1 | string | There are no (further) constraints on this element Element idFamilyMemberHistory.condition.note.text The annotation - text content DefinitionThe text of the annotation.
|
| FamilyMemberHistory | .. | |
| FamilyMemberHistory.extension | 0.. | |
| FamilyMemberHistory.extension | Extension | 0..1 |
| FamilyMemberHistory.extension | Extension | 0.. |
| FamilyMemberHistory.extension.valueReference | .. | |
| FamilyMemberHistory.identifier | .. | |
| FamilyMemberHistory.identifier.system | 1.. | |
| FamilyMemberHistory.identifier.value | 1.. | |
| FamilyMemberHistory.identifier.assigner | Reference(CareConnect-Organization-1) | .. |
| FamilyMemberHistory.patient | Reference(CareConnect-Patient-1) | .. |
| FamilyMemberHistory.relationship | .. | |
| FamilyMemberHistory.relationship.coding | .. | |
| FamilyMemberHistory.relationship.coding | ..1 | |
| FamilyMemberHistory.relationship.coding.extension | 0.. | |
| FamilyMemberHistory.relationship.coding.extension | Extension | 0.. |
| FamilyMemberHistory.relationship.coding.system | 1.. | |
| FamilyMemberHistory.relationship.coding.code | 1.. | |
| FamilyMemberHistory.relationship.coding.display | 1.. | |
| FamilyMemberHistory.gender | .. | |
| FamilyMemberHistory.reasonReference | Reference(QuestionnaireResponse | CareConnect-Observation-1 | CareConnect-Condition-1 | CareConnect-AllergyIntolerance-1) | .. |
| FamilyMemberHistory.note | .. | |
| FamilyMemberHistory.note.author[x] | Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1 | CareConnect-RelatedPerson-1), string | .. |
| FamilyMemberHistory.condition | .. | |
| FamilyMemberHistory.condition.code | .. | |
| FamilyMemberHistory.condition.code.coding | .. | |
| FamilyMemberHistory.condition.code.coding | ..1 | |
| FamilyMemberHistory.condition.code.coding.extension | 0.. | |
| FamilyMemberHistory.condition.code.coding.extension | Extension | 0.. |
| FamilyMemberHistory.condition.code.coding.system | 1.. | |
| FamilyMemberHistory.condition.code.coding.code | 1.. | |
| FamilyMemberHistory.condition.code.coding.display | 1.. | |
| FamilyMemberHistory.condition.outcome | .. | |
| FamilyMemberHistory.condition.outcome.coding | .. | |
| FamilyMemberHistory.condition.outcome.coding | ..1 | |
| FamilyMemberHistory.condition.outcome.coding.extension | 0.. | |
| FamilyMemberHistory.condition.outcome.coding.extension | Extension | 0.. |
| FamilyMemberHistory.condition.outcome.coding.system | 1.. | |
| FamilyMemberHistory.condition.outcome.coding.code | 1.. | |
| FamilyMemberHistory.condition.outcome.coding.display | 1.. | |
| FamilyMemberHistory.condition.note | .. | |
| FamilyMemberHistory.condition.note.author[x] | Reference(CareConnect-Patient-1 | CareConnect-Practitioner-1 | CareConnect-RelatedPerson-1), string | .. |
There is no specific guidance for this profile.
