{
  "description": "This profile represents the constraints applied to the FamilyMemberHistory resource by the PS-CA project. Currently, there is no equivalent IPS UV profile and no ISO CEN IPS 17269 requirements for a family history section. This profile is considered a draft version, and is informed and created as per the requirements of the first jurisdiction (i.e. Alberta) to pilot its use in patient summary within jurisdictional context. The constraints have been compared against other Family Member History FHIR profiles in Canada (OMD Core Data Set, Telus Patient Chart) and Internationally (Swiss Mednet, CareConnect UK, NDHM India) and share many constraints in common with those profiles but represent the minimum requirements as they are known in Canada today. This profile is expected to be refined further as more jurisdictional requirements are defined and as more is known about use in the international patient summary space.",
  "_filename": "structuredefinition-profile-familymemberhistory-ca-ps.json",
  "package_name": "ca.infoway.io.psca",
  "date": "2022-05-18T01:23:00-08:00",
  "derivation": "constraint",
  "publisher": null,
  "fhirVersion": "4.0.1",
  "name": "FamilyMemberHistoryPSCA",
  "abstract": false,
  "copyright": "Copyright © 2024+ Canada Health Infoway. All rights reserved. [Terms of Use and License Agreements](https://ic.infoway-inforoute.ca/en/about/tou). [Privacy Policy](https://www.infoway-inforoute.ca/en/legal/privacy-policy).",
  "type": "FamilyMemberHistory",
  "experimental": "false",
  "resourceType": "StructureDefinition",
  "title": "Family Member History (PS-CA)",
  "package_version": "2.0.0-DFT-Ballot",
  "status": "draft",
  "id": "4d598201-1482-4653-9bd1-34d48510a9ca",
  "kind": "resource",
  "url": "http://fhir.infoway-inforoute.ca/io/psca/StructureDefinition/familymemberhistory-ca-ps",
  "version": null,
  "differential": {
    "element": [ {
      "id": "FamilyMemberHistory.status",
      "path": "FamilyMemberHistory.status",
      "extension": [ {
        "url": "http://hl7.org/fhir/StructureDefinition/structuredefinition-display-hint",
        "valueString": "default: completed"
      } ],
      "mustSupport": true
    }, {
      "id": "FamilyMemberHistory.patient",
      "path": "FamilyMemberHistory.patient",
      "type": [ {
        "code": "Reference",
        "targetProfile": [ "http://fhir.infoway-inforoute.ca/io/psca/StructureDefinition/patient-ca-ps" ]
      } ],
      "mustSupport": true
    }, {
      "id": "FamilyMemberHistory.patient.reference",
      "min": 1,
      "path": "FamilyMemberHistory.patient.reference",
      "mustSupport": true
    }, {
      "id": "FamilyMemberHistory.date",
      "path": "FamilyMemberHistory.date",
      "comment": "This element is not currently flagged as Must Support in PS-CA, as early implementers have indicated the element may not be supported by some piloting systems.\n\n Systems that do support the element are encouraged to include it in generated Patient Summary documents, and support it when received."
    }, {
      "id": "FamilyMemberHistory.relationship",
      "path": "FamilyMemberHistory.relationship",
      "type": [ {
        "code": "CodeableConcept",
        "profile": [ "http://fhir.infoway-inforoute.ca/io/psca/StructureDefinition/CodeableConcept-ca-ps" ]
      } ],
      "mustSupport": true
    }, {
      "id": "FamilyMemberHistory.note",
      "path": "FamilyMemberHistory.note",
      "mustSupport": true
    }, {
      "id": "FamilyMemberHistory.note.text",
      "path": "FamilyMemberHistory.note.text",
      "comment": "Family_History_Notes",
      "mustSupport": true
    }, {
      "id": "FamilyMemberHistory.condition",
      "path": "FamilyMemberHistory.condition",
      "comment": "This element is not currently flagged as Must Support in PS-CA, as early implementers have indicated the element may not be supported by some piloting systems. While the ability to use structured data is desirable, the practice of documenting family member history is still varied and some systems may not have the ability to differentiate individual condition details that are being noted for family members. For initial pilots, implementers should expect that some systems will populate this information as free text in the FamilyMemberHistory.note element. .\n\n Systems that do support the element are encouraged to include it in generated Patient Summary documents, and support it when received."
    }, {
      "id": "FamilyMemberHistory.condition.code",
      "path": "FamilyMemberHistory.condition.code",
      "type": [ {
        "code": "CodeableConcept",
        "profile": [ "http://fhir.infoway-inforoute.ca/io/psca/StructureDefinition/CodeableConcept-ca-ps" ]
      } ]
    }, {
      "id": "FamilyMemberHistory.condition.onset[x]",
      "path": "FamilyMemberHistory.condition.onset[x]",
      "comment": "The data types for this element are not constrained to provide maximum ability for reuse/refinement during draft stage. However, initial implementers using this profile to communicate family history for patient summaries that support semi-structured data for each condition are likely to utilize onsetString."
    }, {
      "id": "FamilyMemberHistory.condition.note.text",
      "path": "FamilyMemberHistory.condition.note.text",
      "mustSupport": true
    } ]
  },
  "baseDefinition": "http://hl7.org/fhir/StructureDefinition/FamilyMemberHistory"
}