FHIR IG Statistics: StructureDefinition/profile-patient

Resources that use this resource

Resources that this resource uses

No resources found

Narrative

No narrative content found in resource

Source

{
  "resourceType": "StructureDefinition",
  "id": "profile-patient",
  "url": "http://pharmacyeclaims.ca/FHIR/v1.0/StructureDefinition/profile-patient",
  "name": "Patient",
  "title": "Patient",
  "status": "draft",
  "description": "Patient details",
  "purpose": "Patient details",
  "fhirVersion": "4.0.1",
  "kind": "resource",
  "abstract": false,
  "type": "Patient",
  "baseDefinition": "http://hl7.org/fhir/StructureDefinition/Patient",
  "derivation": "constraint",
  "differential": {
    "element": [
      {
        "id": "Patient.id",
        "path": "Patient.id",
        "min": 1,
        "mustSupport": true
      },
      {
        "id": "Patient.identifier",
        "path": "Patient.identifier",
        "slicing": {
          "discriminator": [
            {
              "type": "type",
              "path": "$this"
            }
          ],
          "rules": "open"
        },
        "mustSupport": true
      },
      {
        "id": "Patient.identifier:PMSPatientID",
        "path": "Patient.identifier",
        "sliceName": "PMSPatientID",
        "comment": "Usage:  Unique PMS assigned patient identifier.   May be used for validation if there is no JHN.    Note:  This was a request specific to Ontario and will only be populated if requested by an implementer.\r\nCPHA Map:   N/A - new data element",
        "max": "1",
        "mustSupport": true
      },
      {
        "id": "Patient.identifier:PMSPatientID.type",
        "path": "Patient.identifier.type",
        "min": 1,
        "fixedCodeableConcept": {
          "coding": [
            {
              "code": "PLAC"
            }
          ]
        },
        "mustSupport": true
      },
      {
        "id": "Patient.identifier:PMSPatientID.type.coding",
        "path": "Patient.identifier.type.coding",
        "min": 1,
        "max": "1",
        "mustSupport": true
      },
      {
        "id": "Patient.identifier:PMSPatientID.type.coding.system",
        "path": "Patient.identifier.type.coding.system",
        "min": 1,
        "fixedUri": "http://terminology.hl7.org/CodeSystem/v2-0203",
        "mustSupport": true
      },
      {
        "id": "Patient.identifier:PMSPatientID.type.coding.code",
        "path": "Patient.identifier.type.coding.code",
        "min": 1,
        "fixedCode": "PLAC",
        "mustSupport": true
      },
      {
        "id": "Patient.identifier:PMSPatientID.system",
        "path": "Patient.identifier.system",
        "min": 1,
        "mustSupport": true
      },
      {
        "id": "Patient.identifier:PMSPatientID.value",
        "path": "Patient.identifier.value",
        "min": 1,
        "mustSupport": true
      },
      {
        "id": "Patient.name",
        "path": "Patient.name",
        "comment": "Usage Note:  This must be populated when known\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.",
        "mustSupport": true
      },
      {
        "id": "Patient.name.family",
        "path": "Patient.name.family",
        "comment": "Family Name may be decomposed into specific parts using extensions (de, nl, es related cultures).\r\nCPHA - C.38.01 Patient Last Name",
        "mustSupport": true
      },
      {
        "id": "Patient.name.given",
        "path": "Patient.name.given",
        "comment": "If only initials are recorded, they may be used in place of the full name parts. Initials may be separated into multiple given names but often aren't due to paractical limitations.  This element is not called \"first name\" since given names do not always come first.\r\n\r\nCPHA - C.37.01 Patient First Name",
        "mustSupport": true
      },
      {
        "id": "Patient.gender",
        "path": "Patient.gender",
        "comment": "CPHA - C.40.03 Gender\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.",
        "min": 1,
        "mustSupport": true
      },
      {
        "id": "Patient.birthDate",
        "path": "Patient.birthDate",
        "comment": "Usage:  At least an estimated year should be provided as a guess if the real DOB is unknown  There is a standard extension \"patient-birthTime\" available that should be used where Time is required (such as in maternity/infant care systems).\r\n\r\nCPHA - C.34.01 Patient DOB",
        "mustSupport": true
      }
    ]
  }
}