{
"description": null,
"_filename": "profile-patient.StructureDefinition.json",
"package_name": "ForgePatientChart.0830",
"date": "2020-11-09T22:28:57.3566147+00:00",
"derivation": "constraint",
"meta": {
"versionId": "1",
"lastUpdated": "2022-08-24T15:28:42.1148123+00:00"
},
"publisher": null,
"fhirVersion": "4.0.1",
"name": "Patient",
"mapping": [ {
"uri": "http://hl7.org/v3",
"name": "RIM Mapping",
"identity": "rim"
}, {
"uri": "http://hl7.org/v3/cda",
"name": "CDA (R2)",
"identity": "cda"
}, {
"uri": "http://hl7.org/fhir/fivews",
"name": "FiveWs Pattern Mapping",
"identity": "w5"
}, {
"uri": "http://hl7.org/v2",
"name": "HL7 v2 Mapping",
"identity": "v2"
}, {
"uri": "http://loinc.org",
"name": "LOINC code for the element",
"identity": "loinc"
} ],
"abstract": false,
"type": "Patient",
"experimental": null,
"resourceType": "StructureDefinition",
"title": "TELUS Patient",
"package_version": "0.1.0",
"status": "draft",
"id": "82004c38-cf00-49a4-80b7-6e8632ec6080",
"kind": "resource",
"url": "http://telus.com/fhir/patientChart/StructureDefinition/profile-patient",
"version": null,
"differential": {
"element": [ {
"id": "Patient",
"path": "Patient",
"mustSupport": true
}, {
"id": "Patient.id",
"path": "Patient.id",
"comment": "Usage Note: This will usually be a GUID assigned by the sending application.",
"mustSupport": true
}, {
"id": "Patient.meta",
"path": "Patient.meta",
"mustSupport": true
}, {
"id": "Patient.meta.lastUpdated",
"path": "Patient.meta.lastUpdated",
"mustSupport": true
}, {
"id": "Patient.meta.source",
"path": "Patient.meta.source",
"mustSupport": true
}, {
"id": "Patient.meta.profile",
"path": "Patient.meta.profile",
"mustSupport": true
}, {
"id": "Patient.text",
"path": "Patient.text",
"mustSupport": true
}, {
"id": "Patient.extension",
"min": 0,
"path": "Patient.extension",
"slicing": {
"rules": "open",
"discriminator": [ {
"path": "url",
"type": "value"
} ]
}
}, {
"id": "Patient.extension:genderIdentity",
"min": 0,
"path": "Patient.extension",
"type": [ {
"code": "Extension",
"profile": [ "http://hl7.org/fhir/StructureDefinition/patient-genderIdentity" ]
} ],
"sliceName": "genderIdentity",
"isModifier": false,
"mustSupport": true
}, {
"id": "Patient.extension:genderIdentity.value[x]",
"path": "Patient.extension.value[x]",
"slicing": {
"rules": "open",
"discriminator": [ {
"path": "$this",
"type": "type"
} ]
},
"mustSupport": true
}, {
"id": "Patient.extension:genderIdentity.value[x]:valueCodeableConcept",
"path": "Patient.extension.value[x]",
"sliceName": "valueCodeableConcept",
"mustSupport": true
}, {
"path": "Patient.extension",
"min": 0,
"definition": "The pronouns to use when referring to an individual in verbal or written communication",
"isModifier": false,
"type": [ {
"code": "Extension",
"profile": [ "http://telus.com/fhir/patientChart/StructureDefinition/ext-individual-pronouns" ]
} ],
"mustSupport": true,
"sliceName": "Pronouns",
"max": "1",
"id": "Patient.extension:Pronouns",
"comment": "Usage Note: This is a pre-adoption of an HL7 extension, http://hl7.org/fhir/StructureDefinition/individual-pronouns in R5"
}, {
"id": "Patient.identifier",
"path": "Patient.identifier",
"comment": "******** ADD JHN EXTENSION FOR VERSION HERE\r\nUsage Note: For all known profiles, this will be mandatory, with the exception of anonomyized data feeds such as RAPIDs.",
"slicing": {
"rules": "open",
"discriminator": [ {
"path": "type",
"type": "pattern"
} ]
},
"mustSupport": true
}, {
"id": "Patient.identifier.type",
"path": "Patient.identifier.type",
"mustSupport": true
}, {
"id": "Patient.identifier.system",
"min": 1,
"path": "Patient.identifier.system",
"mustSupport": true
}, {
"id": "Patient.identifier.value",
"min": 1,
"path": "Patient.identifier.value",
"mustSupport": true
}, {
"id": "Patient.identifier:MRN",
"max": "1",
"path": "Patient.identifier",
"comment": "Conformance Rule: Sender local patient identifier MAY be stored by the receiving application and used for linking.",
"sliceName": "MRN",
"mustSupport": true
}, {
"id": "Patient.identifier:MRN.type",
"min": 1,
"path": "Patient.identifier.type",
"mustSupport": true,
"patternCodeableConcept": {
"coding": [ {
"code": "MR",
"system": "http://terminology.hl7.org/CodeSystem/v2-0203"
} ]
}
}, {
"id": "Patient.identifier:MRN.type.coding",
"path": "Patient.identifier.type.coding",
"mustSupport": true
}, {
"id": "Patient.identifier:MRN.type.coding.system",
"min": 1,
"path": "Patient.identifier.type.coding.system",
"mustSupport": true
}, {
"id": "Patient.identifier:MRN.type.coding.code",
"min": 1,
"path": "Patient.identifier.type.coding.code",
"fixedCode": "MR",
"mustSupport": true
}, {
"id": "Patient.identifier:MRN.system",
"min": 1,
"path": "Patient.identifier.system",
"comment": "Conformance Rule: This will generally be an OID of the form [Vendor OID].[Application Instance node].1.Suggested format: A branch “.1” is appended to create a unique namespace for the Patient ID.",
"mustSupport": true
}, {
"id": "Patient.identifier:MRN.value",
"min": 1,
"path": "Patient.identifier.value",
"mustSupport": true
}, {
"id": "Patient.identifier:JHN",
"path": "Patient.identifier",
"comment": "Conformance: The TELUS Patient Jurisdictional Health Number Identifier . This must be supplied when known.\r\nUsage Note: There may be multiple active HN's; example, a baby will use the mother's JHN for a period of time before the baby obtains their own PHN. There could also be two if a person is moving from one province to another",
"sliceName": "JHN",
"mustSupport": true
}, {
"id": "Patient.identifier:JHN.type",
"min": 1,
"path": "Patient.identifier.type",
"mustSupport": true,
"patternCodeableConcept": {
"coding": [ {
"code": "JHN",
"system": "http://terminology.hl7.org/CodeSystem/v2-0203"
} ]
}
}, {
"id": "Patient.identifier:JHN.type.coding",
"max": "1",
"min": 1,
"path": "Patient.identifier.type.coding",
"mustSupport": true
}, {
"id": "Patient.identifier:JHN.type.coding.system",
"min": 1,
"path": "Patient.identifier.type.coding.system",
"mustSupport": true
}, {
"id": "Patient.identifier:JHN.type.coding.code",
"min": 1,
"path": "Patient.identifier.type.coding.code",
"fixedCode": "JHN",
"mustSupport": true
}, {
"id": "Patient.identifier:JHN.system",
"min": 1,
"path": "Patient.identifier.system",
"binding": {
"strength": "extensible",
"valueSet": "http://telus.com/fhir/ValueSet/telus-identifier-system-patient-jhn"
},
"comment": "Conformance Rule: This is the OID representing the jurisdictional identifier.\r\n\r\nIf identifier.system is urn:ietf:rfc:3986, then the identifier.value must be a full URI (e.g. start with a scheme).",
"mustSupport": true
}, {
"id": "Patient.identifier:JHN.value",
"min": 1,
"path": "Patient.identifier.value",
"comment": "Conformance Rule: This is the patient's jurisdictional health number\r\n\r\nIf the value is a full URI, then the system must be urn:ietf:rfc:3986.",
"mustSupport": true
}, {
"id": "Patient.name",
"max": "1",
"min": 1,
"path": "Patient.name",
"comment": "Usage: EMRs typically record the name from the healthcard in which case this should be the \"official\" name and should always be sent. Additionally, there is often a preferred name or \"usual\"name in the EMR that should also be sent. Old and/or maiden names can also be helpful for receiving applications who may have existing records with these names. \r\nUsage: If the EMR uses the label \"nickname\", or \"preferred\" name this should map to usual. In PSS, \"preferred\" name will map to \"usual\"; in MA, \"nickname\" will map to \"usual\"\r\n\r\nA patient may have multiple names with different uses or applicable periods. For animals, the name is a \"HumanName\" in the sense that is assigned and used by humans and has the same patterns.",
"slicing": {
"rules": "open",
"discriminator": [ {
"path": "use",
"type": "value"
} ]
},
"mustSupport": true
}, {
"id": "Patient.name.use",
"path": "Patient.name.use",
"comment": "Usage Note: This may be referred to as the Preferred name in some EMRs - this would map to \"usual\".\r\nUsage Note: \"Official\" use should always be present. \"Usual\" should be used for preferred when this name is populated as a separate field in the EMR.\r\n\r\nApplications can assume that a name is current unless it explicitly says that it is temporary or old.",
"mustSupport": true
}, {
"id": "Patient.name.family",
"path": "Patient.name.family",
"mustSupport": true
}, {
"id": "Patient.name.given",
"path": "Patient.name.given",
"mustSupport": true
}, {
"id": "Patient.name.prefix",
"path": "Patient.name.prefix",
"mustSupport": true
}, {
"id": "Patient.name.suffix",
"path": "Patient.name.suffix",
"mustSupport": true
}, {
"id": "Patient.gender",
"path": "Patient.gender",
"comment": "Usage Note: This data is most often captured as a single data element in the EMR. This can also be considered as the Recorded Sex or Gender, that is introduced as an extension in R5. (http://hl7.org/fhir/StructureDefinition/individual-recordedSexOrGender) which will map into this data element. This extension is not used at this point in time. The gender field in the EMRs tend to represent sex at birth, or admin sex or chromosomal sex. Typically this comes from a birth certificate, OHIP/JHN passport, etc - known government identification \r\n\r\nUsage Note: When gender has a value of \"other\" or unknown\", systems may be capable of specifying the \"Sex for Clinical Use\" which an HL7 extension introduced for R5 (http://hl7.org/fhir/StructureDefinition/patient-sexForClinicalUse). This field may be recorded as part of the lab, observation or any other resource where this context is appropriate. \r\n\r\nThe gender might not match the biological sex as determined by genetics or the individual's preferred identification. Note that for both humans and particularly animals, there are other legitimate possibilities than male and female, though the vast majority of systems and contexts only support male and female. Systems providing decision support or enforcing business rules should ideally do this on the basis of Observations dealing with the specific sex or gender aspect of interest (anatomical, chromosomal, social, etc.) However, because these observations are infrequently recorded, defaulting to the administrative gender is common practice. Where such defaulting occurs, rule enforcement should allow for the variation between administrative and biological, chromosomal and other gender aspects. For example, an alert about a hysterectomy on a male should be handled as a warning or overridable error, not a \"hard\" error. See the Patient Gender and Sex section for additional information about communicating patient gender and sex.",
"mustSupport": true
}, {
"id": "Patient.birthDate",
"path": "Patient.birthDate",
"comment": "Usage Note: At least an estimated year should be provided as a guess if the real DOB is unknown.\r\n \r\nUsage Note: There is a standard extension \"patient-birthTime\" available that should be used where Time is required (such as in maternity/infant care systems).",
"mustSupport": true
}, {
"id": "Patient.deceased[x]",
"path": "Patient.deceased[x]",
"mustSupport": true
}, {
"id": "Patient.contact",
"path": "Patient.contact",
"comment": "Usage Rule: Privacy reviews are imperative prior to sharing contact infromation\r\n\r\nContact covers all kinds of contact parties: family members, business contacts, guardians, caregivers. Not applicable to register pedigree and family ties beyond use of having contact.",
"mustSupport": true
}, {
"id": "Patient.contact.relationship",
"path": "Patient.contact.relationship",
"mustSupport": true
}, {
"id": "Patient.contact.relationship.coding",
"path": "Patient.contact.relationship.coding",
"mustSupport": true
}, {
"id": "Patient.contact.relationship.coding.system",
"path": "Patient.contact.relationship.coding.system",
"mustSupport": true
}, {
"id": "Patient.contact.relationship.coding.code",
"path": "Patient.contact.relationship.coding.code",
"mustSupport": true
}, {
"id": "Patient.contact.relationship.coding.display",
"path": "Patient.contact.relationship.coding.display",
"mustSupport": true
}, {
"id": "Patient.contact.name",
"path": "Patient.contact.name",
"mustSupport": true
}, {
"id": "Patient.contact.name.use",
"path": "Patient.contact.name.use",
"mustSupport": true
}, {
"id": "Patient.contact.name.family",
"min": 1,
"path": "Patient.contact.name.family",
"mustSupport": true
}, {
"id": "Patient.contact.name.given",
"path": "Patient.contact.name.given",
"mustSupport": true
}, {
"id": "Patient.contact.telecom",
"path": "Patient.contact.telecom",
"mustSupport": true
}, {
"id": "Patient.contact.telecom.system",
"min": 1,
"path": "Patient.contact.telecom.system",
"mustSupport": true
}, {
"id": "Patient.contact.telecom.value",
"min": 1,
"path": "Patient.contact.telecom.value",
"mustSupport": true
}, {
"id": "Patient.contact.telecom.use",
"path": "Patient.contact.telecom.use",
"mustSupport": true
}, {
"id": "Patient.contact.address",
"path": "Patient.contact.address",
"mustSupport": true
}, {
"id": "Patient.contact.address.use",
"path": "Patient.contact.address.use",
"mustSupport": true
}, {
"id": "Patient.contact.address.line",
"path": "Patient.contact.address.line",
"mustSupport": true
}, {
"id": "Patient.contact.address.city",
"path": "Patient.contact.address.city",
"mustSupport": true
}, {
"id": "Patient.contact.address.state",
"path": "Patient.contact.address.state",
"mustSupport": true
}, {
"id": "Patient.contact.address.postalCode",
"path": "Patient.contact.address.postalCode",
"mustSupport": true
}, {
"id": "Patient.contact.address.country",
"path": "Patient.contact.address.country",
"mustSupport": true
}, {
"id": "Patient.contact.organization",
"path": "Patient.contact.organization",
"comment": "Usage: Example may be family and child services\r\n\r\nReferences SHALL be a reference to an actual FHIR resource, and SHALL be resolveable (allowing for access control, temporary unavailability, etc.). Resolution can be either by retrieval from the URL, or, where applicable by resource type, by treating an absolute reference as a canonical URL and looking it up in a local registry/repository.",
"mustSupport": true
}, {
"id": "Patient.contact.organization.reference",
"path": "Patient.contact.organization.reference",
"mustSupport": true
}, {
"id": "Patient.contact.organization.display",
"path": "Patient.contact.organization.display",
"mustSupport": true
}, {
"id": "Patient.communication",
"path": "Patient.communication",
"mustSupport": true
}, {
"id": "Patient.communication.language",
"path": "Patient.communication.language",
"mustSupport": true
}, {
"id": "Patient.communication.language.coding",
"path": "Patient.communication.language.coding",
"mustSupport": true
}, {
"id": "Patient.communication.language.coding.system",
"path": "Patient.communication.language.coding.system",
"mustSupport": true
}, {
"id": "Patient.communication.language.coding.code",
"path": "Patient.communication.language.coding.code",
"mustSupport": true
}, {
"id": "Patient.communication.language.text",
"path": "Patient.communication.language.text",
"mustSupport": true
}, {
"id": "Patient.generalPractitioner",
"path": "Patient.generalPractitioner",
"comment": "Usage note: Provider reference to the organization and the practitioner resource \r\nIf a patient has not been assigned a doctor at the clinic only provide reference to the organization (parent organization)\r\n\r\nWhen a Primary MD/NP for that provider at that clinic is assigned provide reference to the organization or in some cases, the sub-organization (eg conceptual location in EMRs where two orgs exist under the same application instance) and the practitioner \r\n\r\nUsage Note: Primary and secondary providers in PSS are determined by the appointment system. ***Further discussion is required to determine how this would be conveyed in FHIR. \r\n\r\nThis may be the primary care provider (in a GP context), or it may be a patient nominated care manager in a community/disability setting, or even organization that will provide people to perform the care provider roles. It is not to be used to record Care Teams, these should be in a CareTeam resource that may be linked to the CarePlan or EpisodeOfCare resources.\nMultiple GPs may be recorded against the patient for various reasons, such as a student that has his home GP listed along with the GP at university during the school semesters, or a \"fly-in/fly-out\" worker that has the onsite GP also included with his home GP to remain aware of medical issues.\n\nJurisdictions may decide that they can profile this down to 1 if desired, or 1 per type.",
"mustSupport": true
}, {
"id": "Patient.generalPractitioner.reference",
"path": "Patient.generalPractitioner.reference",
"mustSupport": true
}, {
"id": "Patient.generalPractitioner.display",
"path": "Patient.generalPractitioner.display",
"mustSupport": true
}, {
"id": "Patient.managingOrganization",
"path": "Patient.managingOrganization",
"comment": "Usage note: This should be populated with a particular Org (parent organization with the EMR instance) that is associated with the patient. \r\n\r\nThere is only one managing organization for a specific patient record. Other organizations will have their own Patient record, and may use the Link property to join the records together (or a Person resource which can include confidence ratings for the association).",
"mustSupport": true
}, {
"id": "Patient.managingOrganization.reference",
"min": 1,
"path": "Patient.managingOrganization.reference",
"comment": "Usage Note: Either the identifier or reference may be used.\r\n\r\nUsing absolute URLs provides a stable scalable approach suitable for a cloud/web context, while using relative/logical references provides a flexible approach suitable for use when trading across closed eco-system boundaries. Absolute URLs do not need to point to a FHIR RESTful server, though this is the preferred approach. If the URL conforms to the structure \"/[type]/[id]\" then it should be assumed that the reference is to a FHIR RESTful server.",
"mustSupport": true
}, {
"id": "Patient.managingOrganization.display",
"path": "Patient.managingOrganization.display",
"mustSupport": true
} ]
},
"baseDefinition": "http://hl7.org/fhir/StructureDefinition/Patient"
}