{
"description": "This is closely synchronized with the Family Member History Profile created by the TELUS DW Team",
"_filename": "profile-family-member-history.json",
"package_name": "ForgePatientChart.0830",
"date": "2022-04-26T16:03:59.2029703+00:00",
"derivation": "constraint",
"meta": {
"versionId": "3",
"lastUpdated": "2022-07-27T19:49:44.310632+00:00"
},
"publisher": null,
"fhirVersion": "4.0.1",
"name": "FamilyMemberHistory",
"abstract": false,
"type": "FamilyMemberHistory",
"experimental": null,
"resourceType": "StructureDefinition",
"title": "Family Member History Patient Chart",
"package_version": "0.1.0",
"status": "draft",
"id": "f65e7bfd-8fd1-4885-a33d-67004b22aeca",
"kind": "resource",
"url": "https://telus.com/fhir/patientChart/StructureDefinition/profile-family-member-history",
"version": null,
"differential": {
"element": [ {
"id": "FamilyMemberHistory",
"path": "FamilyMemberHistory",
"comment": "Note: This is closely synchronized with the Family Member History Profile created by the TELUS DW Team"
}, {
"id": "FamilyMemberHistory.id",
"path": "FamilyMemberHistory.id",
"comment": "Unique identifier from the EMR \r\n\r\nThe only time that a resource does not have an id is when it is being submitted to the server using a create operation.",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.meta",
"path": "FamilyMemberHistory.meta",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.meta.lastUpdated",
"path": "FamilyMemberHistory.meta.lastUpdated",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.meta.source",
"path": "FamilyMemberHistory.meta.source",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.meta.profile",
"path": "FamilyMemberHistory.meta.profile",
"comment": "Usage: Each impelmentation project will determine support for this data element. It may be useful for validating a message instance against this profile.\r\n\r\nIt 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": true
}, {
"id": "FamilyMemberHistory.text",
"path": "FamilyMemberHistory.text",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.status",
"path": "FamilyMemberHistory.status",
"comment": "EMR --> FHIR\r\nNeeds Review --> partial\r\ndocumented without any flag for needs review or unfinished --> completed\r\ndeleted --> entered in error \r\n\r\nThis element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.patient",
"path": "FamilyMemberHistory.patient",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.patient.reference",
"path": "FamilyMemberHistory.patient.reference",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.date",
"path": "FamilyMemberHistory.date",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.relationship",
"path": "FamilyMemberHistory.relationship",
"comment": "Usage Note: Must be codified when mapping is possible.\r\n\r\nPS Suite: May be present as discrete data, but is commonly part of a string. Will be provided when available.\r\nMedAccess: May be present as discrete data. Will be provided when available.\r\n\r\nNot 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": true
}, {
"id": "FamilyMemberHistory.relationship.coding",
"path": "FamilyMemberHistory.relationship.coding",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.relationship.coding.system",
"code": [ {
"system": "http://terminology.hl7.org/ValueSet/v3-FamilyMember"
} ],
"path": "FamilyMemberHistory.relationship.coding.system",
"fixedUri": "https://tgateway.infoway-inforoute.ca/vs/familymemberrelationshipcode",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.relationship.coding.code",
"code": [ {
"system": "https://fhir.infoway-inforoute.ca/ValueSet/familymemberrelationshipcode",
"version": "2.0.0"
} ],
"path": "FamilyMemberHistory.relationship.coding.code",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.relationship.text",
"min": 1,
"path": "FamilyMemberHistory.relationship.text",
"comment": "Usage note \r\nMA - Concatnate Relation and maternal/paternal fields together\r\nPSS - Family member field if documented in structured formate. Otherwise provide full short description \r\n\r\nVery often the text is the same as a displayName of one of the codings.",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.deceased[x]",
"path": "FamilyMemberHistory.deceased[x]",
"comment": "PS Suite: Available when entered as structured data Depending on documentation could be sent as deceasedBoolean or deceasedstring\r\nMed Access: N/A",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.note",
"path": "FamilyMemberHistory.note",
"comment": "PS Suite: When data not enterted in a structured format text string will be provided \r\nMed Access: Notes will be provided where available\r\n\r\nFor 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": true
}, {
"id": "FamilyMemberHistory.condition",
"path": "FamilyMemberHistory.condition",
"comment": "PS Suite: Available when when family history is coded but will likely not be available for most patients\r\nMed Access: Provide when available",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.condition.code",
"path": "FamilyMemberHistory.condition.code",
"comment": "Usage Note: This may be codified using ICD-9, ICD-10, SNOMED, ENCODE (Ontario area) or any other available coding system. \r\n\r\nNot 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": true
}, {
"id": "FamilyMemberHistory.condition.code.coding",
"code": [ {
"system": "http://hl7.org/fhir/sid/icd9"
}, {
"system": "http://snomed.info/sct"
} ],
"path": "FamilyMemberHistory.condition.code.coding",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.condition.code.coding.system",
"path": "FamilyMemberHistory.condition.code.coding.system",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.condition.code.coding.code",
"path": "FamilyMemberHistory.condition.code.coding.code",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.condition.code.text",
"min": 1,
"path": "FamilyMemberHistory.condition.code.text",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.condition.outcome",
"path": "FamilyMemberHistory.condition.outcome",
"comment": "PS Suite: Available when entered as structured data\r\nMed Access: Available when documented \r\n\r\nNot 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": true
}, {
"id": "FamilyMemberHistory.condition.outcome.text",
"path": "FamilyMemberHistory.condition.outcome.text",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.condition.onset[x]",
"path": "FamilyMemberHistory.condition.onset[x]",
"comment": "PS Suite: Include start date document as date, age or string\r\nMed Access: Include onset date as datetime \r\n\r\nThe 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": true
}, {
"id": "FamilyMemberHistory.condition.note",
"path": "FamilyMemberHistory.condition.note",
"mustSupport": true
}, {
"id": "FamilyMemberHistory.condition.note.text",
"path": "FamilyMemberHistory.condition.note.text",
"comment": "PSS - Long details \r\nMA - Note on the task panel related to condition\r\n\r\nSystems 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/"
} ]
},
"baseDefinition": "http://hl7.org/fhir/StructureDefinition/FamilyMemberHistory"
}