FHIR Chat · docs / Issue #49 should open-imaging-study have an option... · fhircast-github

Stream: fhircast-github

Topic: docs / Issue #49 should open-imaging-study have an option...

---

Github Notifications (FHIRcast) (Dec 11 2018 at 17:20):

isaacvetter opened Issue #49

In the Event catalog, we currently define open, switch and close events for an imaging study. open-imaging-study and switch-imaging-study are defined to have the following context:

Context	Optionality	FHIR operation to generate context	Description
patient	Optional	Patient/{id}?_elements=identifier	FHIR Patient resource describing the patient whose chart is currently in context.
study	Required	ImagingStudy/{id}?_elements=identifier,accession	FHIR ImagingStudy resource in context. Note that in addition to the request identifier and accession elements, the DICOM uid and FHIR patient reference are included because they're required by the FHIR specification.

Whereas, for the similar open-patient-chart event, we specify Encounter as optional context:

Context	Optionality	FHIR operation to generate context	Description
patient	Required	Patient/{id}?_elements=identifier	FHIR Patient resource describing the patient whose chart is currently in context..
encounter	Optional	Encounter/{id}?_elements=identifier	FHIR Encounter resource in context in the newly opened patient's chart.

Is there any reason why encounter context shouldn't also optionally be part of the imaging events?

Github Notifications (FHIRcast) (Feb 05 2019 at 14:30):

isaacvetter assigned Issue #49(assigned to isaacvetter)

In the Event catalog, we currently define open, switch and close events for an imaging study. open-imaging-study and switch-imaging-study are defined to have the following context:

Context	Optionality	FHIR operation to generate context	Description
patient	Optional	Patient/{id}?_elements=identifier	FHIR Patient resource describing the patient whose chart is currently in context.
study	Required	ImagingStudy/{id}?_elements=identifier,accession	FHIR ImagingStudy resource in context. Note that in addition to the request identifier and accession elements, the DICOM uid and FHIR patient reference are included because they're required by the FHIR specification.

Whereas, for the similar open-patient-chart event, we specify Encounter as optional context:

Context	Optionality	FHIR operation to generate context	Description
patient	Required	Patient/{id}?_elements=identifier	FHIR Patient resource describing the patient whose chart is currently in context..
encounter	Optional	Encounter/{id}?_elements=identifier	FHIR Encounter resource in context in the newly opened patient's chart.

Is there any reason why encounter context shouldn't also optionally be part of the imaging events?

Github Notifications (FHIRcast) (Feb 05 2019 at 14:31):

isaacvetter commented on Issue #49

In conversation with @lbergnehr and @Will Maethner, we discussed that it is common for more general purpose CPOE, PACS and dictation systems for have an Encounter alongside an ImagingStudy, although specialty systems (e.g. EKG) may not.

Definitely Encounter should not be required, but does seem to make sense as optional.

Github Notifications (FHIRcast) (Feb 05 2019 at 22:56):

will commented on Issue #49

Hello I'm @will but I have not discussed that, I promise. I made an EKG in school once with like 3 op amps, and that was kinda neat, but i have no idea what any of this is.

Github Notifications (FHIRcast) (Feb 05 2019 at 22:57):

will commented on Issue #49

it's super simple to make really


Github Notifications (FHIRcast) (Feb 06 2019 at 04:01):

isaacvetter edited a comment on Issue #49

In conversation with @lbergnehr and @wmaethner, we discussed that it is common for more general purpose CPOE, PACS and dictation systems for have an Encounter alongside an ImagingStudy, although specialty systems (e.g. EKG) may not.

Definitely Encounter should not be required, but does seem to make sense as optional.

Github Notifications (FHIRcast) (Feb 06 2019 at 04:02):

isaacvetter deleted a comment on Issue #49

Hello I'm @will but I have not discussed that, I promise. I made an EKG in school once with like 3 op amps, and that was kinda neat, but i have no idea what any of this is.

Github Notifications (FHIRcast) (Feb 06 2019 at 04:02):

isaacvetter deleted a comment on Issue #49

it's super simple to make really


Github Notifications (FHIRcast) (Feb 06 2019 at 04:03):

isaacvetter commented on Issue #49

(@will - thanks for the fascinating diagram, sorry for deleting your posts.)

---

Last updated: Apr 12 2022 at 19:14 UTC