This is a list of use cases supported by this specification. These use cases are implemented in the scenarios section.

Patient demographics

Use Cases for patient demographics and administrative patient records

Use Case 1

This is a basic use case of first creating and then updating a patient record.

• Patient Pia Peters’s record is created

• Patient’s record is updated with name, address (in Brussels), the SSIN, nationality and birth place.

 

Allergies and intolerance reporting

Use Case 1

This the basic use case where an allergy record is created, shared and updated.

• Patient reports an allergy to Penicillin

• GP records a suspected allergy to Penicillin

• Specialist performs tests and sees that the suspected reaction is na expectable adverse reaction to Penicillin and updates the allergy record to Refuted

• GP consults the allergy and sees it is updated

Validation: This use case is implemented in the Allergy scenario.

 

Use Case 2

This use case shows that the allergy agent should be coded but that may not always be the case – sometimes it is possible to have only text.

• Patient goes to GP and says they are allergic to “Coquilles St. Jacques”.

• The GP searches for “Coquilles St. Jacques” in the list of allergens. Since this is not found in the terminology server, the GP enters only the text.

• The admission secretary searches the terminology server for concepts and finds that the nearest expression is “pétoncle” and encodes that information.

 

Use Case 3

This use case shows that the allergy record is no longer static but a live record, so there is a risk of outdated information.

• Patient has a record of a suspected allergy.

• Patient goes to hospital before going to specialist to confirm the allergy. The ER physician tries to access allergy and since it is not yet marked as refuted, the ER physician assumes that the allergy reaction is active and updates the allergy record.

• Meanwhile the specialist wants to update the record but now the allergy record is already different, with more reactions.

 

Use Case 4

This use case shows what happens with the data custody: Who is responsible for the record after the record is updated.

• The patient visits the GP after the emergency and after seeign the specialist.

• The GP consults the allergies (after the ER physician updating the allergy information with a new reaction, and the specialist updating the allergy to “refuted”).

• The GP must assess if the allergy is really refuted or the reaction that took the patient to the ER is actually an allergy to another substance.

• The GP must then update the records accordingly.

Communication and Journaling

Use Case 1

This use case contains several interactions among the members of a care team, exchanging different notifications

• System notifies practitioner when an event is due

• Nurse sends a message to the team - in different languages

• Caregiver replies to message

• Nurse issues a note with attachments (e.g. a picture)

• Physician forwards a message to another participant

 

Validation: This use case is implemented in the Communication and Journal scenario.

 

Care Team definition

Use Case 1

This use case shows a basic interaction when assembling a team.

• Patient Pia Peters sees the GP who wants to start a diabetes care plan

• Physician starts a team for attending a patient, assigning only a nurse (by role, not a specific nurse)

• A nurse is assigned to start the team and composes a proposed team for a care plan, including the GP, a specialist, the nurse, the care giver, the patient’s daughter and the Dienstencentrum that will provide assistance when needed.

• After checking availabilities and any constraints, the team gets approved (status "active")

Validation: This use case is implemented in the Home Care Team scenario.