Stream: implementers
Topic: Pre registration
Bettina Lieske (Jun 21 2018 at 14:54):
Hello,
Bettina Lieske (Jun 21 2018 at 14:55):
We would like to model a pre-registration of a patient where a preliminary (non validated) patient record is created and a set of other resources like
- Appointment
- Planned encounter
- Preliminary diagnoses
- Planned healthcare services, procedures
- etc. would need to be created.
We were wondering how to implement this in the best standardized way? Is there any implementation guide for this type of use case?
We also have some very specific questions:
1) How can we model a "pre registration patient"? Through the status active = false (this does not really fit as the record is not “entered in error” as described in the documentation.
2) How to model the pre registration encounter? Class = PRE REG, and status = planned? It seems that there are some dependencies between these 2 elements. Are they specified somewhere?
Lloyd McKenzie (Jun 21 2018 at 17:33):
@Brian Postlethwaite
Simone Heckmann (Jul 02 2018 at 06:55):
In your use case, the Encounter.status would definitely be "planned". Encounter.class depends on what you are planning for (could be anything: inpatient, ambulatory, virtual...
I don't think these two are interdependent, except perhaps in so far as "planned emergencies" are rather unlikely to happen...
Last updated: Apr 12 2022 at 19:14 UTC
