<status value="draft" /> <date value="2022-04-26T16:03:59.2029703+00:00" /> <description value="This is closely synchronized with the Family Member History Profile created by the TELUS DW Team" /> <fhirVersion value="4.0.1" /> <kind value="resource" /> <abstract value="false" /> <type value="FamilyMemberHistory" /> <baseDefinition value="http://hl7.org/fhir/StructureDefinition/FamilyMemberHistory" /> <derivation value="constraint" /> <differential> <element id="FamilyMemberHistory"> <path value="FamilyMemberHistory" /> <comment value="Note: This is closely synchronized with the Family Member History Profile created by the TELUS DW Team" /> </element> <element id="FamilyMemberHistory.id"> <path value="FamilyMemberHistory.id" /> <comment value="Unique identifier from the EMR The only time that a resource does not have an id is when it is being submitted to the server using a create operation." /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.meta"> <path value="FamilyMemberHistory.meta" /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.meta.lastUpdated"> <path value="FamilyMemberHistory.meta.lastUpdated" /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.meta.source"> <path value="FamilyMemberHistory.meta.source" /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.meta.profile"> <path value="FamilyMemberHistory.meta.profile" /> <comment value="Usage: Each impelmentation project will determine support for this data element. It may be useful for validating a message instance against this profile. It is up to the server and/or other infrastructure of policy to determine whether/how these claims are verified and/or updated over time. The list of profile URLs is a set." /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.text"> <path value="FamilyMemberHistory.text" /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.status"> <path value="FamilyMemberHistory.status" /> <comment value="EMR --> FHIR Needs Review --> partial documented without any flag for needs review or unfinished --> completed deleted --> entered in error This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid." /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.patient"> <path value="FamilyMemberHistory.patient" /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.patient.reference"> <path value="FamilyMemberHistory.patient.reference" /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.date"> <path value="FamilyMemberHistory.date" /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.relationship"> <path value="FamilyMemberHistory.relationship" /> <comment value="Usage Note: Must be codified when mapping is possible. PS Suite: May be present as discrete data, but is commonly part of a string. Will be provided when available. MedAccess: May be present as discrete data. Will be provided when available. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination." /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.relationship.coding"> <path value="FamilyMemberHistory.relationship.coding" /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.relationship.coding.system"> <path value="FamilyMemberHistory.relationship.coding.system" /> <code> <system value="http://terminology.hl7.org/ValueSet/v3-FamilyMember" /> </code> <fixedUri value="https://tgateway.infoway-inforoute.ca/vs/familymemberrelationshipcode" /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.relationship.coding.code"> <path value="FamilyMemberHistory.relationship.coding.code" /> <code> <system value="https://fhir.infoway-inforoute.ca/ValueSet/familymemberrelationshipcode" /> <version value="2.0.0" /> </code> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.relationship.text"> <path value="FamilyMemberHistory.relationship.text" /> <comment value="Usage note MA - Concatnate Relation and maternal/paternal fields together PSS - Family member field if documented in structured formate. Otherwise provide full short description Very often the text is the same as a displayName of one of the codings." /> <min value="1" /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.deceased[x]"> <path value="FamilyMemberHistory.deceased[x]" /> <comment value="PS Suite: Available when entered as structured data Depending on documentation could be sent as deceasedBoolean or deceasedstring Med Access: N/A" /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.note"> <path value="FamilyMemberHistory.note" /> <comment value="PS Suite: When data not enterted in a structured format text string will be provided Med Access: Notes will be provided where available For systems that do not have structured annotations, they can simply communicate a single annotation with no author or time. This element may need to be included in narrative because of the potential for modifying information. *Annotations SHOULD NOT* be used to communicate "modifying" information that could be computable. (This is a SHOULD because enforcing user behavior is nearly impossible)." /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.condition"> <path value="FamilyMemberHistory.condition" /> <comment value="PS Suite: Available when when family history is coded but will likely not be available for most patients Med Access: Provide when available" /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.condition.code"> <path value="FamilyMemberHistory.condition.code" /> <comment value="Usage Note: This may be codified using ICD-9, ICD-10, SNOMED, ENCODE (Ontario area) or any other available coding system. Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination." /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.condition.code.coding"> <path value="FamilyMemberHistory.condition.code.coding" /> <code> <system value="http://hl7.org/fhir/sid/icd9" /> </code> <code> <system value="http://snomed.info/sct" /> </code> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.condition.code.coding.system"> <path value="FamilyMemberHistory.condition.code.coding.system" /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.condition.code.coding.code"> <path value="FamilyMemberHistory.condition.code.coding.code" /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.condition.code.text"> <path value="FamilyMemberHistory.condition.code.text" /> <min value="1" /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.condition.outcome"> <path value="FamilyMemberHistory.condition.outcome" /> <comment value="PS Suite: Available when entered as structured data Med Access: Available when documented Not all terminology uses fit this general pattern. In some cases, models should not use CodeableConcept and use Coding directly and provide their own structure for managing text, codings, translations and the relationship between elements and pre- and post-coordination." /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.condition.outcome.text"> <path value="FamilyMemberHistory.condition.outcome.text" /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.condition.onset[x]"> <path value="FamilyMemberHistory.condition.onset[x]" /> <comment value="PS Suite: Include start date document as date, age or string Med Access: Include onset date as datetime The context of use may frequently define what kind of quantity this is and therefore what kind of units can be used. The context of use may also restrict the values for the comparator." /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.condition.note"> <path value="FamilyMemberHistory.condition.note" /> <mustSupport value="true" /> </element> <element id="FamilyMemberHistory.condition.note.text"> <path value="FamilyMemberHistory.condition.note.text" /> <comment value="PSS - Long details MA - Note on the task panel related to condition Systems are not required to have markdown support, so the text should be readable without markdown processing. The markdown syntax is GFM - see https://github.github.com/gfm/" /> </element> </differential> </StructureDefinition>