Stream: implementers
Topic: Best way to create a clinical note
Abhas Arya (Dec 29 2020 at 07:14):
I have a patient-facing app where patients respond to questions about certain symptoms. I'd like to ideally write their responses, along with some other data, back into Epic.
I am trying to figure out the best mechanism to save a document under a patient. I believe Clinical Notes would be a good option. Epic provides the DocumentReference (Clinical Notes) Resource, which has a Create option (STU3).
However, it seems the new standard is DSTU2. So will I still be able to create a clinical note with an Epic organization using DSTU2 or not? Also is this the best resource to write an arbitrarily formatted document to?
Lloyd McKenzie (Dec 29 2020 at 16:43):
STU3 is newer than DSTU2. And interfaces will soon move to R4. DocumentReference is the agreed solution for clinical notes
Cooper Thompson (Dec 29 2020 at 17:05):
Epic only supports creating clinical notes in STU3 and R4. We don't support notes in DSTU2.
Abhas Arya (Dec 29 2020 at 21:29):
but most hospitals according to epic's website are on DSTU2. Will this pose an issue for creating clinical notes? For example, I'm working with Yale medical center. Their epic implementation is on DSTU2.
Abhas Arya (Dec 29 2020 at 21:34):
Also, thanks for clarifying the versioning. R4 is the latest version, preceded by STU3, preceded by DSTU2
Cooper Thompson (Dec 30 2020 at 15:28):
The open.epic endpoint directory is only the list of publicly available FHIR endpoints for Epic customers. Health systems can also deploy private FHIR endpoints. Additionally, turning on STU3 and R4 is fairly easy. You can work with the Yale IT team to enable the STU3 or R4 endpoint for your application.
Last updated: Apr 12 2022 at 19:14 UTC
