This track is postponed for Connectathon 26. 

Track overview

Short Description


To address the emerging COVID-19 treatment challenges, clinicians are encouraged to rely on electronic clinical data to determine which patients should be prioritized for being tested, hospitalized, and/or isolated. Failure to include or exclude patients in COVID-19 screening, testing, and treatment could lead to life-threatening situations for patients and could impact the overall trajectory of the outbreak at a population-level.

COVID-19 symptoms and pre-existing conditions are important to triage patient triage and FHIR resources and implementation guides can be used to record patient-reported information, create findings/observation, and then apply them to business process automation. (see additional background). Semantic interoperabity requires an integrated terminology knowledge base that allows sharing information provided by patients with EHR rercord information about problem lists (e.g., diabetes, cancer treatment). 

This track is supporting project Guidelines for a Standardized Terminology Knowledge base Project.

Long Description

This track is demonstrating the process of collecting and applying medical triage questionnaire to pre-arrival evaluation processes for suspected COVID-19 patients. 

It uses the following resources:

Additionally, this track is validating BPM+ process automation (BPM process description for pre-arrival triage)  and fulfilling a set of clinical and interoperability objectives and provides value to clinicians and improved outcomes for patients,


Type

Applicable:

Submitting Work Group/Project/Accelerator/Affiliate/Implementer Group



Proposed Track Lead

Ioana Singureanu ioana.singureanu at bookzurman.com  - track lead, Standards Architect
Keith E. Campbell  MD, PhD - Subject Matter Expert


Related tracks

None

FHIR Version

Specification(s) this track uses

Please provide version-specific (ballot, connectathon or official release) hyperlinks to the FHIR IG or other specifications implementers of this track will follow.  If the relevant version does not exist yet, describe what it *will* be.  (Hyperlink to actual version should be present no later than 1 month prior to connectathon.)

Artifacts of focus


Clinical input requested (if any)

Does your track have a need for input from the clinical community?  If so, what are the needs?


Patient input requested (if any)

Does your track have a need for input from the patient/care-giver community?  If so, what are the needs?


Expected participants

Who do you expect to be present?  How many do you expect to attend?


Zulip stream

https://chat.fhir.org/#narrow/stream/256830-BPM_plus_covid_19_workflows

#BPM_plus_covid_19_workflows


Track Orientation

Provide information about the date & time at which a webinar will be hosted to share further participation information about this track.  (Mandatory)


Track details

System Roles

Describe each type of system that could participate in the track
Please include information here regarding how much advance preparation will be required if creating a client and/or server.


Role 1 Name

Scenarios

Describe the different scenarios participating systems can engage in during the connectathon.  Each scenario should provide sufficient description that participants can appropriately construct their software in advance to prepare to interoperate during the connectathon.

Scenario Step 1 Name

Action:

Precondition:

Success Criteria:

Bonus point:

TestScript(s)

Indicate any test scripts that will be used to help verify system behavior


Security and Privacy Considerations

Identify any expectations around security (e.g. will TLS, mutual-TLS, OAuth, etc. be required to participate