Add MedicationStatement Examples From AU Core IG

Mar 11, 2025 by ADMIN 49 views

**Adding MedicationStatement Examples from AU Core IG**

Introduction

The Australian Core (AU Core) Implementation Guide (IG) provides a set of FHIR resources and profiles that are tailored to the Australian healthcare landscape. One of the key resources in the AU Core IG is the MedicationStatement profile, which is used to represent a patient's medication history. In this article, we will explore the addition of MedicationStatement examples to the AU Core IG, which are designed to demonstrate the use of this profile in a real-world scenario.

MedicationStatement Profile

The MedicationStatement profile is a key resource in the AU Core IG, and it is used to represent a patient's medication history. This profile is designed to capture information about a patient's medications, including the medication name, dosage, frequency, and reason for taking the medication. The profile also includes a set of elements that are flagged as Must Support, which means that these elements must be present in any instance of the MedicationStatement resource.

MedicationStatement Examples

The AU Core IG includes a set of MedicationStatement examples that are designed to demonstrate the use of this profile in a real-world scenario. These examples are intended to show how the MedicationStatement profile can be used to represent a patient's medication history, and they include a range of different scenarios, such as:

An instance of all elements and slices flagged with Must Support
Profile specific implementation guidance on contained medication (i.e. an instance of a contained medication)
Profile specific implementation guidance on reasonCode OR reasonReference
Medicine Information page
Additional AUCDI elements mapped to dosage but not flagged with Must Support

Referential Integrity

The MedicationStatement examples in the AU Core IG are designed to demonstrate referential integrity, which means that the resources are linked together in a way that ensures data consistency and accuracy. For example, the subject of the MedicationStatement resource is a relative reference to the Patient resource, and the reasonReference is a relative reference to the Condition resource.

Example 1: MedicationStatement with all elements and slices flagged with Must Support

The following is an example of a MedicationStatement resource that includes all elements and slices flagged with Must Support:

{
  "resourceType": "MedicationStatement",
  "id": "example-1",
  "subject": {
    "reference": "Patient/banks-mia-leanne"
  },
  "effectiveDateTime": "2022-01-01",
  "medication": {
    "reference": "Medication/paracetamol"
  },
  "dose": {
    "quantity": {
      "value": 2,
      "unit": "tablet"
    },
    "timing": {
      "repeat": {
        "frequency": 2,
        "period": 1
      }
    }
  },
  "reasonCode": {
    "coding": [
      {
        "system": "http://hl7.org/fhir/sid/icd-10-au",
        "code": "M54.1"
      }
    ]
  },
  "reasonReference": {
    "reference": "Condition/uti"
  }
}

This example shows how the MedicationStatement profile can be used to represent a patient's medication history, including the medication name, dosage, frequency, and reason for taking the medication.

Example 2: MedicationStatement with profile specific implementation guidance on contained medication

The following is an example of a MedicationStatement resource that includes profile specific implementation guidance on contained medication:

{
  "resourceType": "MedicationStatement",
  "id": "example-2",
  "subject": {
    "reference": "Patient/banks-mia-leanne"
  },
  "effectiveDateTime": "2022-01-01",
  "medication": {
    "reference": "Medication/paracetamol"
  },
  "dose": {
    "quantity": {
      "value": 2,
      "unit": "tablet"
    },
    "timing": {
      "repeat": {
        "frequency": 2,
        "period": 1
      }
    }
  },
  "contained": [
    {
      "resourceType": "Medication",
      "id": "contained-1",
      "code": {
        "coding": [
          {
            "system": "http://hl7.org/fhir/sid/icd-10-au",
            "code": "M54.1"
          }
        ]
      }
    }
  ]
}

This example shows how the MedicationStatement profile can be used to represent a patient's medication history, including the medication name, dosage, frequency, and reason for taking the medication, as well as contained medication information.

Conclusion

Introduction

The Australian Core (AU Core) Implementation Guide (IG) provides a set of FHIR resources and profiles that are tailored to the Australian healthcare landscape. One of the key resources in the AU Core IG is the MedicationStatement profile, which is used to represent a patient's medication history. In this article, we will answer some frequently asked questions about the MedicationStatement examples from the AU Core IG.

Q: What is the purpose of the MedicationStatement examples in the AU Core IG?

A: The MedicationStatement examples in the AU Core IG are designed to demonstrate the use of the MedicationStatement profile in a real-world scenario. These examples are intended to show how the MedicationStatement profile can be used to represent a patient's medication history, and they include a range of different scenarios, such as an instance of all elements and slices flagged with Must Support, profile specific implementation guidance on contained medication, and profile specific implementation guidance on reasonCode OR reasonReference.

Q: What is the difference between the MedicationStatement profile and the Medication resource?

A: The MedicationStatement profile and the Medication resource are two different FHIR resources that are used to represent different aspects of a patient's medication history. The Medication resource is used to represent a specific medication, such as a tablet or a liquid, while the MedicationStatement profile is used to represent a patient's medication history, including the medication name, dosage, frequency, and reason for taking the medication.

**Q: What is the significance of the Must Support elements in the MedicationStatement profile?**

A: The Must Support elements in the MedicationStatement profile are elements that must be present in any instance of the MedicationStatement resource. These elements are flagged as Must Support because they are critical to the accurate representation of a patient's medication history.

Q: How do the MedicationStatement examples in the AU Core IG demonstrate referential integrity?

A: The MedicationStatement examples in the AU Core IG demonstrate referential integrity by linking the MedicationStatement resource to other FHIR resources, such as the Patient resource and the Condition resource. This ensures that the data is consistent and accurate across different resources.

Q: What is the difference between the reasonCode and reasonReference elements in the MedicationStatement profile?

A: The reasonCode and reasonReference elements in the MedicationStatement profile are used to represent different types of reasons for taking a medication. The reasonCode element is used to represent a specific reason for taking a medication, such as a medical condition, while the reasonReference element is used to represent a reference to a Condition resource that provides more information about the reason for taking the medication.

Q: How can I use the MedicationStatement examples in the AU Core IG to improve my FHIR implementation?

A: The MedicationStatement examples in the AU Core IG can be used to improve your FHIR implementation by providing a real-world example of how to use the MedicationStatement profile to represent a patient's medication history. These examples can help you to understand how to use the Must Support elements, how to demonstrate referential integrity, and how to use the reasonCode and reasonReference elements.

Conclusion

In conclusion, the MedicationStatement examples from the AU Core IG provide a valuable resource for healthcare professionals and developers who are working with FHIR resources and profiles. These examples demonstrate the use of the MedicationStatement profile in a real-world scenario, and they provide a range of different scenarios, such as an instance of all elements and slices flagged with Must Support, profile specific implementation guidance on contained medication, and profile specific implementation guidance on reasonCode OR reasonReference. By using these examples, healthcare professionals and developers can gain a better understanding of how to use the MedicationStatement profile to represent a patient's medication history, and they can ensure that their FHIR resources and profiles are accurate and consistent.