Skip to end of metadata
Go to start of metadata





1a. Project Name

SMART Web Messaging

1b. Project ID

1597

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact being Reaffirmed or proceeding to Normative directly after being either Informative or STU?

No

1e. Today's Date

1f. Name of standard being reaffirmed

1g. Project Artifact Information

1h. ISO/IEC Standard to Adopt

1i. Does the standard include excerpted text from one or more ISO, IEC or ISO/IEC standards, but is not an identical or modified adoption?

1j. Unit of Measure

2a. Primary/Sponsor WG

FHIR Infrastructure

2b. Co-Sponsor WG

Clinical Decision Support

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Update Periods

At WGMs and prior to ballot

2b. Co-Sponsor WG 2

Implementable Technology Specifications

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2b. Co-Sponsor WG 3

Security

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Involvement

At WGMs and prior to ballot

2d. Project Facilitator

Carl Anderson

2e. Other Interested Parties (and roles)

Josh Mandel
Brett Marquard

2f. Modeling Facilitator

Josh Mandel

2g. Publishing Facilitator

Carl Anderson

2h. Vocabulary Facilitator

Josh Mandel

2i. Domain Expert Representative

Brett Marquard

2j. Business Requirements Analyst

Brett Marquard

2k. Conformance Facilitator

Josh Mandel

2l. Other Facilitators

Brett Marquard

2m. Implementers

Evidence Care
The T-System
Cerner
Epic

3a. Project Scope

SMART Web Messaging enables tight UI integration between EHRs and embedded SMART apps via HTML5's Web Messaging. Use SMART Web Messaging to push unsigned orders, note snippets, risk scores or UI suggestions directly to the clinician's EHR session. Built on the browser's javascript window.postMessage function, SMART Web Messaging is a simple, native API for health apps embedded within the user's workflow.

Attachments

3b. Project Need

Within a clinical workflow system (such as an EHR), SMART apps can be launched automatically at specific points in the workflow, or on demand in response to a user interaction, including clicking on a suggestion from a CDS Hooks service. Once launched, a web app is typically embedded within a patient’s chart and communicates with the EHR via RESTful FHIR APIs. These RESTful APIs are great for CRUD operations on a database, but don’t enable tight workflow integration or access to draft FHIR resources that may only exist in memory on the EHR client.

3c. Security Risk

No

3d. External Drivers

3e. Objectives/Deliverables and Target Dates

Ballot the specification as STU in Sept 2020
Publish by Dec. 31, 2020

3f. Common Names / Keywords / Aliases:

3g. Lineage

3h. Project Dependencies

3i. HL7-Managed Project Document Repository URL:

https://github.com/hl7/smart-web-messaging

3j. Backwards Compatibility

No

3k. Additional Backwards Compatibility Information (if applicable)

3l. Using Current V3 Data Types?

N/A

3l. Reason for not using current V3 data types?

3m. External Vocabularies

3n. List of Vocabularies

3o. Earliest prior release and/or version to which the compatibility applies

4a. Products

FHIR Implementation Guide, Guidance (e.g. Companion Guide, Cookbook, etc), New Product Definition

4b. For FHIR IGs and FHIR Profiles, what product version(s) will the profiles apply to?

4c. FHIR Profiles Version

4d. Please define your New Product Definition

4d. Please define your New Product Family

5a. Project Intent

Create new standard, Implementation Guide (IG) will be created/modified

5a. White Paper Type

5a. Is the project adopting/endorsing an externally developed IG?

No

5a. Externally developed IG is to be (select one)

5a. Specify external organization

5a. Revising Current Standard Info

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

Argonaut Accelerator Project, part of the PAMA use case in 2019

5d. Joint Copyright

No

5e. I understand I must submit a Joint Copyright Letter of Agreement to the TSC in order for the PSS to receive TSC approval.

no

6a. External Project Collaboration

6b. Content Already Developed

6c. Content externally developed?

Yes

6d. List Developers of Externally Developed Content

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Standards Development Organizations (SDOs)

6f. Other Stakeholders

6g. Vendors

EHR, PHR, Health Care IT

6g. Other Vendors

6h. Providers

Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6h. Other Providers

6i. Realm

Universal

7d. US Realm Approval Date

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Jan 13, 2020

7c. Co-Sponsor Approval Date

Jan 15, 2020

7c. Co-Sponsor 2 Approval Date

May 19, 2020

7c. Co-Sponsor 3 Approval Date

May 26, 2020

7c. Co-Sponsor 4 Approval Date

7c. Co-Sponsor 5 Approval Date

7c. Co-Sponsor 6 Approval Date

7c. Co-Sponsor 7 Approval Date

7c. Co-Sponsor 8 Approval Date

7c. Co-Sponsor 9 Approval Date

7c. Co-Sponsor 10 Approval Date

7e. CDA MG Approval Date

7f. FMG Approval Date

May 06, 2020

7g. V2 MG Approval Date

7h. Architecture Review Board Approval Date

May 21, 2020

7i. Steering Division Approval Date

May 16, 2020

7j. TSC Approval Date

Jun 01, 2020


 Show Changes

Version

13

Modifier

Brett Marquard

Modify Date

Jun 01, 2020 15:25

1a. Project Name

SMART Web Messaging

1b. Project ID

1597

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

FHIR Infrastructure

2b. Co-Sponsor WG

Clinical Decision Support

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Update Periods

At WGMs and prior to ballot

2b. Co-Sponsor WG 2

Implementable Technology Specifications

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Involvement

At WGMs and prior to ballot

2d. Project Facilitator

Carl Anderson

2e. Other Interested Parties (and roles)

Josh Mandel
Brett Marquard

2f. Modeling Facilitator

Josh Mandel

2g. Publishing Facilitator

Carl Anderson

2h. Vocabulary Facilitator

Josh Mandel

2i. Domain Expert Representative

Brett Marquard

2j. Business Requirements Analyst

Brett Marquard

2k. Conformance Facilitator

Josh Mandel

2l. Other Facilitators

Brett Marquard

2m. Implementers

Evidence Care
The T-System
Cerner
Epic

3a. Project Scope

SMART Web Messaging enables tight UI integration between EHRs and embedded SMART apps via HTML5's Web Messaging. Use SMART Web Messaging to push unsigned orders, note snippets, risk scores or UI suggestions directly to the clinician's EHR session. Built on the browser's javascript window.postMessage function, SMART Web Messaging is a simple, native API for health apps embedded within the user's workflow.

3b. Project Need

Within a clinical workflow system (such as an EHR), SMART apps can be launched automatically at specific points in the workflow, or on demand in response to a user interaction, including clicking on a suggestion from a CDS Hooks service. Once launched, a web app is typically embedded within a patient’s chart and communicates with the EHR via RESTful FHIR APIs. These RESTful APIs are great for CRUD operations on a database, but don’t enable tight workflow integration or access to draft FHIR resources that may only exist in memory on the EHR client.

3c. Security Risk

No

3e. Objectives/Deliverables and Target Dates

Ballot the specification as STU in Sept 2020
Publish by Dec. 31, 2020

3i. HL7-Managed Project Document Repository URL:

https://github.com/hl7/smart-web-messaging

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

4a. Products

FHIR Implementation Guide, Guidance (e.g. Companion Guide, Cookbook, etc), New Product Definition

5a. Project Intent

Create new standard, Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

Argonaut Accelerator Project, part of the PAMA use case in 2019

5d. Joint Copyright

No

6c. Content externally developed?

Yes

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Jan 13, 2020

7c. Co-Sponsor Approval Date

Jan 15, 2020

7c. Co-Sponsor 2 Approval Date

May 19, 2020

7c. Co-Sponsor 3 Approval Date

May 26, 2020

7f. FMG Approval Date

May 06, 2020

7h. Architecture Review Board Approval Date

May 21, 2020

7i. Steering Division Approval Date

May 16, 2020

7j. TSC Approval Date

Jun 01, 2020

Version

12

Modifier

Brett Marquard

Modify Date

May 26, 2020 19:20

1a. Project Name

SMART Web Messaging

1b. Project ID

1597

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

FHIR Infrastructure

2b. Co-Sponsor WG

Clinical Decision Support

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Update Periods

At WGMs and prior to ballot

2b. Co-Sponsor WG 2

Implementable Technology Specifications

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Involvement

At WGMs and prior to ballot

2d. Project Facilitator

Carl Anderson

2e. Other Interested Parties (and roles)

Josh Mandel
Brett Marquard

2f. Modeling Facilitator

Josh Mandel

2g. Publishing Facilitator

Carl Anderson

2h. Vocabulary Facilitator

Josh Mandel

2i. Domain Expert Representative

Brett Marquard

2j. Business Requirements Analyst

Brett Marquard

2k. Conformance Facilitator

Josh Mandel

2l. Other Facilitators

Brett Marquard

2m. Implementers

Evidence Care
The T-System
Cerner
Epic

3a. Project Scope

SMART Web Messaging enables tight UI integration between EHRs and embedded SMART apps via HTML5's Web Messaging. Use SMART Web Messaging to push unsigned orders, note snippets, risk scores or UI suggestions directly to the clinician's EHR session. Built on the browser's javascript window.postMessage function, SMART Web Messaging is a simple, native API for health apps embedded within the user's workflow.

3b. Project Need

Within a clinical workflow system (such as an EHR), SMART apps can be launched automatically at specific points in the workflow, or on demand in response to a user interaction, including clicking on a suggestion from a CDS Hooks service. Once launched, a web app is typically embedded within a patient’s chart and communicates with the EHR via RESTful FHIR APIs. These RESTful APIs are great for CRUD operations on a database, but don’t enable tight workflow integration or access to draft FHIR resources that may only exist in memory on the EHR client.

3c. Security Risk

No

3e. Objectives/Deliverables and Target Dates

Ballot the specification as STU in Sept 2020
Publish by Dec. 31, 2020

3i. HL7-Managed Project Document Repository URL:

https://github.com/hl7/smart-web-messaging

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

4a. Products

FHIR Implementation Guide, Guidance (e.g. Companion Guide, Cookbook, etc), New Product Definition

5a. Project Intent

Create new standard, Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

Argonaut Accelerator Project, part of the PAMA use case in 2019

5d. Joint Copyright

No

6c. Content externally developed?

Yes

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Jan 13, 2020

7c. Co-Sponsor Approval Date

Jan 15, 2020

7c. Co-Sponsor 2 Approval Date

May 19, 2020

7c. Co-Sponsor 3 Approval Date

May 26, 2020

7f. FMG Approval Date

May 06, 2020

7h. Architecture Review Board Approval Date

May 21, 2020

7i. Steering Division Approval Date

May 16, 2020

Version

11

Modifier

Anne Wizauer

Modify Date

May 26, 2020 13:11

1a. Project Name

SMART Web Messaging

1b. Project ID

1597

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

FHIR Infrastructure

2b. Co-Sponsor WG

Clinical Decision Support

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Update Periods

At WGMs and prior to ballot

2b. Co-Sponsor WG 2

Implementable Technology Specifications

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2d. Project Facilitator

Carl Anderson

2e. Other Interested Parties (and roles)

Josh Mandel
Brett Marquard

2f. Modeling Facilitator

Josh Mandel

2g. Publishing Facilitator

Carl Anderson

2h. Vocabulary Facilitator

Josh Mandel

2i. Domain Expert Representative

Brett Marquard

2j. Business Requirements Analyst

Brett Marquard

2k. Conformance Facilitator

Josh Mandel

2l. Other Facilitators

Brett Marquard

2m. Implementers

Evidence Care
The T-System
Cerner
Epic

3a. Project Scope

SMART Web Messaging enables tight UI integration between EHRs and embedded SMART apps via HTML5's Web Messaging. Use SMART Web Messaging to push unsigned orders, note snippets, risk scores or UI suggestions directly to the clinician's EHR session. Built on the browser's javascript window.postMessage function, SMART Web Messaging is a simple, native API for health apps embedded within the user's workflow.

3b. Project Need

Within a clinical workflow system (such as an EHR), SMART apps can be launched automatically at specific points in the workflow, or on demand in response to a user interaction, including clicking on a suggestion from a CDS Hooks service. Once launched, a web app is typically embedded within a patient’s chart and communicates with the EHR via RESTful FHIR APIs. These RESTful APIs are great for CRUD operations on a database, but don’t enable tight workflow integration or access to draft FHIR resources that may only exist in memory on the EHR client.

3c. Security Risk

No

3e. Objectives/Deliverables and Target Dates

Ballot the specification as STU in Sept 2020
Publish by Dec. 31, 2020

3i. HL7-Managed Project Document Repository URL:

https://github.com/hl7/smart-web-messaging

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

4a. Products

FHIR Implementation Guide, Guidance (e.g. Companion Guide, Cookbook, etc), New Product Definition

5a. Project Intent

Create new standard, Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

Argonaut Accelerator Project, part of the PAMA use case in 2019

5d. Joint Copyright

No

6c. Content externally developed?

Yes

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Jan 13, 2020

7c. Co-Sponsor Approval Date

Jan 15, 2020

7c. Co-Sponsor 2 Approval Date

May 19, 2020

7f. FMG Approval Date

May 06, 2020

7h. Architecture Review Board Approval Date

May 21, 2020

7i. Steering Division Approval Date

May 16, 2020

Version

10

Modifier

Brett Marquard

Modify Date

May 19, 2020 18:24

1a. Project Name

SMART Web Messaging

1b. Project ID

1597

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

FHIR Infrastructure

2b. Co-Sponsor WG

Clinical Decision Support

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Update Periods

At WGMs and prior to ballot

2b. Co-Sponsor WG 2

Implementable Technology Specifications

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2d. Project Facilitator

Carl Anderson

2e. Other Interested Parties (and roles)

Josh Mandel
Brett Marquard

2f. Modeling Facilitator

Josh Mandel

2g. Publishing Facilitator

Carl Anderson

2h. Vocabulary Facilitator

Josh Mandel

2i. Domain Expert Representative

Brett Marquard

2j. Business Requirements Analyst

Brett Marquard

2k. Conformance Facilitator

Josh Mandel

2l. Other Facilitators

Brett Marquard

2m. Implementers

Evidence Care
The T-System
Cerner
Epic

3a. Project Scope

SMART Web Messaging enables tight UI integration between EHRs and embedded SMART apps via HTML5's Web Messaging. Use SMART Web Messaging to push unsigned orders, note snippets, risk scores or UI suggestions directly to the clinician's EHR session. Built on the browser's javascript window.postMessage function, SMART Web Messaging is a simple, native API for health apps embedded within the user's workflow.

3b. Project Need

Within a clinical workflow system (such as an EHR), SMART apps can be launched automatically at specific points in the workflow, or on demand in response to a user interaction, including clicking on a suggestion from a CDS Hooks service. Once launched, a web app is typically embedded within a patient’s chart and communicates with the EHR via RESTful FHIR APIs. These RESTful APIs are great for CRUD operations on a database, but don’t enable tight workflow integration or access to draft FHIR resources that may only exist in memory on the EHR client.

3c. Security Risk

No

3e. Objectives/Deliverables and Target Dates

Ballot the specification as STU in Sept 2020
Publish by Dec. 31, 2020

3i. HL7-Managed Project Document Repository URL:

https://github.com/hl7/smart-web-messaging

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

4a. Products

FHIR Implementation Guide, Guidance (e.g. Companion Guide, Cookbook, etc), New Product Definition

5a. Project Intent

Create new standard, Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

Argonaut Accelerator Project, part of the PAMA use case in 2019

5d. Joint Copyright

No

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Jan 13, 2020

7c. Co-Sponsor Approval Date

Jan 15, 2020

7c. Co-Sponsor 2 Approval Date

May 19, 2020

7f. FMG Approval Date

May 06, 2020

7i. Steering Division Approval Date

May 16, 2020

Version

9

Modifier

Anne Wizauer

Modify Date

May 18, 2020 13:47

1a. Project Name

SMART Web Messaging

1b. Project ID

1597

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

FHIR Infrastructure

2b. Co-Sponsor WG

Clinical Decision Support

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Update Periods

At WGMs and prior to ballot

2b. Co-Sponsor WG 2

Implementable Technology Specifications

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2d. Project Facilitator

Carl Anderson

2e. Other Interested Parties (and roles)

Josh Mandel
Brett Marquard

2f. Modeling Facilitator

Josh Mandel

2g. Publishing Facilitator

Carl Anderson

2h. Vocabulary Facilitator

Josh Mandel

2i. Domain Expert Representative

Brett Marquard

2j. Business Requirements Analyst

Brett Marquard

2k. Conformance Facilitator

Josh Mandel

2l. Other Facilitators

Brett Marquard

2m. Implementers

Evidence Care
The T-System
Cerner
Epic

3a. Project Scope

SMART Web Messaging enables tight UI integration between EHRs and embedded SMART apps via HTML5's Web Messaging. Use SMART Web Messaging to push unsigned orders, note snippets, risk scores or UI suggestions directly to the clinician's EHR session. Built on the browser's javascript window.postMessage function, SMART Web Messaging is a simple, native API for health apps embedded within the user's workflow.

3b. Project Need

Within a clinical workflow system (such as an EHR), SMART apps can be launched automatically at specific points in the workflow, or on demand in response to a user interaction, including clicking on a suggestion from a CDS Hooks service. Once launched, a web app is typically embedded within a patient’s chart and communicates with the EHR via RESTful FHIR APIs. These RESTful APIs are great for CRUD operations on a database, but don’t enable tight workflow integration or access to draft FHIR resources that may only exist in memory on the EHR client.

3c. Security Risk

No

3e. Objectives/Deliverables and Target Dates

Ballot the specification as STU in Sept 2020
Publish by Dec. 31, 2020

3i. HL7-Managed Project Document Repository URL:

https://github.com/hl7/smart-web-messaging

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

4a. Products

FHIR Implementation Guide, Guidance (e.g. Companion Guide, Cookbook, etc), New Product Definition

5a. Project Intent

Create new standard, Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

Argonaut Accelerator Project, part of the PAMA use case in 2019

5d. Joint Copyright

No

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Jan 13, 2020

7c. Co-Sponsor Approval Date

Jan 15, 2020

7f. FMG Approval Date

May 06, 2020

7i. Steering Division Approval Date

May 16, 2020

Version

8

Modifier

Brett Marquard

Modify Date

May 13, 2020 19:41

1a. Project Name

SMART Web Messaging

1b. Project ID

1597

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

FHIR Infrastructure

2b. Co-Sponsor WG

Clinical Decision Support

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Update Periods

At WGMs and prior to ballot

2b. Co-Sponsor WG 2

Implementable Technology Specifications

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2d. Project Facilitator

Carl Anderson

2e. Other Interested Parties (and roles)

Josh Mandel
Brett Marquard

2f. Modeling Facilitator

Josh Mandel

2g. Publishing Facilitator

Carl Anderson

2h. Vocabulary Facilitator

Josh Mandel

2i. Domain Expert Representative

Brett Marquard

2j. Business Requirements Analyst

Brett Marquard

2k. Conformance Facilitator

Josh Mandel

2l. Other Facilitators

Brett Marquard

2m. Implementers

Evidence Care
The T-System
Cerner
Epic

3a. Project Scope

SMART Web Messaging enables tight UI integration between EHRs and embedded SMART apps via HTML5's Web Messaging. Use SMART Web Messaging to push unsigned orders, note snippets, risk scores or UI suggestions directly to the clinician's EHR session. Built on the browser's javascript window.postMessage function, SMART Web Messaging is a simple, native API for health apps embedded within the user's workflow.

3b. Project Need

Within a clinical workflow system (such as an EHR), SMART apps can be launched automatically at specific points in the workflow, or on demand in response to a user interaction, including clicking on a suggestion from a CDS Hooks service. Once launched, a web app is typically embedded within a patient’s chart and communicates with the EHR via RESTful FHIR APIs. These RESTful APIs are great for CRUD operations on a database, but don’t enable tight workflow integration or access to draft FHIR resources that may only exist in memory on the EHR client.

3c. Security Risk

No

3e. Objectives/Deliverables and Target Dates

Ballot the specification as STU in Sept 2020
Publish by Dec. 31, 2020

3i. HL7-Managed Project Document Repository URL:

https://github.com/hl7/smart-web-messaging

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

4a. Products

FHIR Implementation Guide, Guidance (e.g. Companion Guide, Cookbook, etc), New Product Definition

5a. Project Intent

Create new standard, Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

Argonaut Accelerator Project, part of the PAMA use case in 2019

5d. Joint Copyright

No

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Jan 13, 2020

7c. Co-Sponsor Approval Date

Jan 15, 2020

7f. FMG Approval Date

May 06, 2020

Version

7

Modifier

Carl Anderson

Modify Date

May 13, 2020 17:31

1a. Project Name

SMART Web Messaging

1b. Project ID

1597

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

FHIR Infrastructure

2b. Co-Sponsor WG

Clinical Decision Support

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Update Periods

At WGMs and prior to ballot

2b. Co-Sponsor WG 2

Implementable Technology Specifications

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2d. Project Facilitator

Carl Anderson

2e. Other Interested Parties (and roles)

Josh Mandel
Brett Marquard

2f. Modeling Facilitator

Josh Mandel

2g. Publishing Facilitator

Carl Anderson

2h. Vocabulary Facilitator

Josh Mandel

2i. Domain Expert Representative

Brett Marquard

2j. Business Requirements Analyst

Brett Marquard

2k. Conformance Facilitator

Josh Mandel

2l. Other Facilitators

Brett Marquard

2m. Implementers

Evidence Care
The T-System
Cerner
Epic

3a. Project Scope

SMART Web Messaging enables tight UI integration between EHRs and embedded SMART apps via HTML5's Web Messaging. Use SMART Web Messaging to push unsigned orders, note snippets, risk scores or UI suggestions directly to the clinician's EHR session. Built on the browser's javascript window.postMessage function, SMART Web Messaging is a simple, native API for health apps embedded within the user's workflow.

3b. Project Need

Within a clinical workflow system (such as an EHR), SMART apps can be launched automatically at specific points in the workflow, or on demand in response to a user interaction, including clicking on a suggestion from a CDS Hooks service. Once launched, a web app is typically embedded within a patient’s chart and communicates with the EHR via RESTful FHIR APIs. These RESTful APIs are great for CRUD operations on a database, but don’t enable tight workflow integration or access to draft FHIR resources that may only exist in memory on the EHR client.

3e. Objectives/Deliverables and Target Dates

Ballot the specification as STU in Sept 2020
Publish by Dec. 31, 2020

3i. HL7-Managed Project Document Repository URL:

https://github.com/hl7/smart-web-messaging

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

4a. Products

FHIR Implementation Guide, Guidance (e.g. Companion Guide, Cookbook, etc), New Product Definition

5a. Project Intent

Create new standard, Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

Argonaut Accelerator Project, part of the PAMA use case in 2019

5d. Joint Copyright

No

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Jan 13, 2020

7c. Co-Sponsor Approval Date

Jan 15, 2020

7f. FMG Approval Date

May 06, 2020

Version

6

Modifier

Carl Anderson

Modify Date

May 11, 2020 16:00

1a. Project Name

SMART Web Messaging

1b. Project ID

1597

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

FHIR Infrastructure

2b. Co-Sponsor WG

Clinical Decision Support

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Update Periods

At WGMs and prior to ballot

2b. Co-Sponsor WG 2

Implementable Technology Specifications

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2d. Project Facilitator

Carl Anderson

2e. Other Interested Parties (and roles)

Josh Mandel
Brett Marquard

2f. Modeling Facilitator

Josh Mandel

2g. Publishing Facilitator

Carl Anderson

2h. Vocabulary Facilitator

Josh Mandel

2i. Domain Expert Representative

Brett Marquard

2j. Business Requirements Analyst

Brett Marquard

2k. Conformance Facilitator

Josh Mandel

2l. Other Facilitators

Brett Marquard

2m. Implementers

Evidence Care
T-Systems
Cerner
Epic

3a. Project Scope

SMART Web Messaging enables tight UI integration between EHRs and embedded SMART apps via HTML5's Web Messaging. Use SMART Web Messaging to push unsigned orders, note snippets, risk scores or UI suggestions directly to the clinician's EHR session. Built on the browser's javascript window.postMessage function, SMART Web Messaging is a simple, native API for health apps embedded within the user's workflow.

3b. Project Need

Within a clinical workflow system (such as an EHR), SMART apps can be launched automatically at specific points in the workflow, or on demand in response to a user interaction, including clicking on a suggestion from a CDS Hooks service. Once launched, a web app is typically embedded within a patient’s chart and communicates with the EHR via RESTful FHIR APIs. These RESTful APIs are great for CRUD operations on a database, but don’t enable tight workflow integration or access to draft FHIR resources that may only exist in memory on the EHR client.

3e. Objectives/Deliverables and Target Dates

Ballot the specification as STU in Sept 2020
Publish by Dec. 31, 2020

3i. HL7-Managed Project Document Repository URL:

https://github.com/hl7/smart-web-messaging

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

4a. Products

FHIR Implementation Guide, Guidance (e.g. Companion Guide, Cookbook, etc), New Product Definition

5a. Project Intent

Create new standard, Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

Argonaut Accelerator Project, part of the PAMA use case in 2019

5d. Joint Copyright

No

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Jan 13, 2020

7c. Co-Sponsor Approval Date

Jan 15, 2020

7f. FMG Approval Date

May 06, 2020

Version

5

Modifier

Carl Anderson

Modify Date

May 11, 2020 15:44

1a. Project Name

SMART Web Messaging

1b. Project ID

1597

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

FHIR Infrastructure

2b. Co-Sponsor WG

Clinical Decision Support

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Update Periods

At WGMs and prior to ballot

2b. Co-Sponsor WG 2

Implementable Technology Specifications

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2d. Project Facilitator

Carl Anderson

2e. Other Interested Parties (and roles)

Josh Mandel
Brett Marquard

2k. Conformance Facilitator

Josh Mandel

2l. Other Facilitators

Brett Marquard

2m. Implementers

Evidence Care
T-Systems
Cerner
Epic

3a. Project Scope

SMART Web Messaging enables tight UI integration between EHRs and embedded SMART apps via HTML5's Web Messaging. Use SMART Web Messaging to push unsigned orders, note snippets, risk scores or UI suggestions directly to the clinician's EHR session. Built on the browser's javascript window.postMessage function, SMART Web Messaging is a simple, native API for health apps embedded within the user's workflow.

3b. Project Need

Within a clinical workflow system (such as an EHR), SMART apps can be launched automatically at specific points in the workflow, or on demand in response to a user interaction, including clicking on a suggestion from a CDS Hooks service. Once launched, a web app is typically embedded within a patient’s chart and communicates with the EHR via RESTful FHIR APIs. These RESTful APIs are great for CRUD operations on a database, but don’t enable tight workflow integration or access to draft FHIR resources that may only exist in memory on the EHR client.

3e. Objectives/Deliverables and Target Dates

Ballot the specification as STU in Sept 2020
Publish by Dec. 31, 2020

3i. HL7-Managed Project Document Repository URL:

https://github.com/hl7/smart-web-messaging

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

4a. Products

FHIR Implementation Guide, Guidance (e.g. Companion Guide, Cookbook, etc), New Product Definition

5a. Project Intent

Create new standard, Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

Argonaut Accelerator Project, part of the PAMA use case in 2019

5d. Joint Copyright

No

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Jan 13, 2020

7c. Co-Sponsor Approval Date

Jan 15, 2020

7f. FMG Approval Date

May 06, 2020

Version

4

Modifier

Carl Anderson

Modify Date

May 06, 2020 21:09

1a. Project Name

SMART Web Messaging

1b. Project ID

1597

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

FHIR Infrastructure

2b. Co-Sponsor WG

Clinical Decision Support

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Update Periods

At WGMs and prior to ballot

2b. Co-Sponsor WG 2

Implementable Technology Specifications

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2d. Project Facilitator

Carl Anderson

2e. Other Interested Parties (and roles)

Josh Mandel
Brett Marquard

2k. Conformance Facilitator

Josh Mandel

2l. Other Facilitators

Brett Marquard

2m. Implementers

Evidence Care
T-Systems
Cerner
Epic

3a. Project Scope

SMART Web Messaging enables tight UI integration between EHRs and embedded SMART apps via HTML5's Web Messaging. Use SMART Web Messaging to push unsigned orders, note snippets, risk scores or UI suggestions directly to the clinician's EHR session. Built on the browser's javascript window.postMessage function, SMART Web Messaging is a simple, native API for health apps embedded within the user's workflow.

3b. Project Need

Within a clinical workflow system (such as an EHR), SMART apps can be launched automatically at specific points in the workflow, or on demand in response to a user interaction, including clicking on a suggestion from a CDS Hooks service. Once launched, a web app is typically embedded within a patient’s chart and communicates with the EHR via RESTful FHIR APIs. These RESTful APIs are great for CRUD operations on a database, but don’t enable tight workflow integration or access to draft FHIR resources that may only exist in memory on the EHR client.

3e. Objectives/Deliverables and Target Dates

Ballot the specification as STU in Sept 2020
Publish by Dec. 31, 2020

3i. HL7-Managed Project Document Repository URL:

tbd

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

4a. Products

FHIR Implementation Guide, Guidance (e.g. Companion Guide, Cookbook, etc), New Product Definition

5a. Project Intent

Create new standard, Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

Argonaut Accelerator Project, part of the PAMA use case in 2019

5d. Joint Copyright

No

6c. Content externally developed?

No

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Jan 13, 2020

7c. Co-Sponsor Approval Date

Jan 15, 2020

7f. FMG Approval Date

May 06, 2020

Version

3

Modifier

Carl Anderson

Modify Date

May 06, 2020 21:00

1a. Project Name

SMART Web Messaging

1b. Project ID

1597

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

FHIR Infrastructure

2b. Co-Sponsor WG

Clinical Decision Support

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Update Periods

At WGMs and prior to ballot

2b. Co-Sponsor WG 2

Implementable Technology Specifications

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2d. Project Facilitator

Carl Anderson

2e. Other Interested Parties (and roles)

Josh Mandel
Brett Marquard

2k. Conformance Facilitator

Josh Mandel

2l. Other Facilitators

Brett Marquard

2m. Implementers

Evidence Care
T-Systems
Cerner
Epic

3a. Project Scope

SMART Web Messaging enables tight UI integration between EHRs and embedded SMART apps via HTML5's Web Messaging. Use SMART Web Messaging to push unsigned orders, note snippets, risk scores or UI suggestions directly to the clinician's EHR session. Built on the browser's javascript window.postMessage function, SMART Web Messaging is a simple, native API for health apps embedded within the user's workflow.

3b. Project Need

Within a clinical workflow system (such as an EHR), SMART apps can be launched automatically at specific points in the workflow, or on demand in response to a user interaction, including clicking on a suggestion from a CDS Hooks service. Once launched, a web app is typically embedded within a patient’s chart and communicates with the EHR via RESTful FHIR APIs. These RESTful APIs are great for CRUD operations on a database, but don’t enable tight workflow integration or access to draft FHIR resources that may only exist in memory on the EHR client.

3e. Objectives/Deliverables and Target Dates

Ballot the specification as STU in Sept 2020
Publish by Dec. 31, 2020

3i. HL7-Managed Project Document Repository URL:

tbd

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

4a. Products

FHIR Implementation Guide, Guidance (e.g. Companion Guide, Cookbook, etc), New Product Definition

5a. Project Intent

Create new standard, Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

Argonaut Accelerator Project, part of the PAMA use case in 2019

5d. Joint Copyright

No

6c. Content externally developed?

No

6d. List Developers of Externally Developed Content

SMART, Argonaut

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Jan 13, 2020

7c. Co-Sponsor Approval Date

Jan 15, 2020

7f. FMG Approval Date

May 06, 2020

Version

2

Modifier

Carl Anderson

Modify Date

May 06, 2020 20:44

1a. Project Name

SMART Web Messaging

1b. Project ID

1597

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

FHIR Infrastructure

2b. Co-Sponsor WG

Clinical Decision Support

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Update Periods

At WGMs and prior to ballot

2d. Project Facilitator

Carl Anderson

2e. Other Interested Parties (and roles)

Josh Mandel
Brett Marquard

2k. Conformance Facilitator

Josh Mandel

2l. Other Facilitators

Brett Marquard

2m. Implementers

Evidence Care
T-Systems
Cerner
Epic

3a. Project Scope

SMART Web Messaging enables tight UI integration between EHRs and embedded SMART apps via HTML5's Web Messaging. Use SMART Web Messaging to push unsigned orders, note snippets, risk scores or UI suggestions directly to the clinician's EHR session. Built on the browser's javascript window.postMessage function, SMART Web Messaging is a simple, native API for health apps embedded within the user's workflow.

3b. Project Need

Within a clinical workflow system (such as an EHR), SMART apps can be launched automatically at specific points in the workflow, or on demand in response to a user interaction, including clicking on a suggestion from a CDS Hooks service. Once launched, a web app is typically embedded within a patient’s chart and communicates with the EHR via RESTful FHIR APIs. These RESTful APIs are great for CRUD operations on a database, but don’t enable tight workflow integration or access to draft FHIR resources that may only exist in memory on the EHR client.

3e. Objectives/Deliverables and Target Dates

Ballot the specification as STU in Sept 2020
Publish by Dec. 31, 2020

3i. HL7-Managed Project Document Repository URL:

tbd

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

4a. Products

FHIR Implementation Guide, Guidance (e.g. Companion Guide, Cookbook, etc), New Product Definition

5a. Project Intent

Create new standard, Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5b. Project Ballot Type

STU to Normative

5c. Additional Ballot Info

Argonaut Accelerator Project, part of the PAMA use case in 2019

5d. Joint Copyright

No

6c. Content externally developed?

No

6d. List Developers of Externally Developed Content

SMART, Argonaut

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Jan 13, 2020

7c. Co-Sponsor Approval Date

Jan 15, 2020

7f. FMG Approval Date

May 06, 2020

Version

1

Modifier

Brett Marquard

Modify Date

May 05, 2020 23:49

1a. Project Name

SMART Web Messaging

1b. Project ID

1597

1c. Is Your Project an Investigative Project (aka PSS-Lite)?

No

1d. Is your Project Artifact now proceeding to Normative directly or after being either Informative or STU?

No

2a. Primary/Sponsor WG

FHIR Infrastructure

2b. Co-Sponsor WG

Clinical Decision Support

2c. Co-Sponsor Level of Involvement

Request periodic project updates; specify period in text box below (e.g. 'Monthly', 'At WGMs', etc.)

2c. Co-Sponsor Update Periods

At WGMs and prior to ballot

2d. Project Facilitator

Carl Anderson

2e. Other Interested Parties (and roles)

Josh Mandel
Brett Marquard

2k. Conformance Facilitator

Josh Mandel

2l. Other Facilitators

Brett Marquard

2m. Implementers

Evidence Care
T-Systems
Cerner
Epic

3a. Project Scope

SMART Web Messaging enables tight UI integration between EHRs and embedded SMART apps via HTML5's Web Messaging. Use SMART Web Messaging to push unsigned orders, note snippets, risk scores or UI suggestions directly to the clinician's EHR session. Built on the browser's javascript window.postMessage function, SMART Web Messaging is a simple, native API for health apps embedded within the user's workflow.

3b. Project Need

Within a clinical workflow system (such as an EHR), SMART apps can be launched automatically at specific points in the workflow, or on demand in response to a user interaction, including clicking on a suggestion from a CDS Hooks service. Once launched, a web app is typically embedded within a patient’s chart and communicates with the EHR via RESTful FHIR APIs. These RESTful APIs are great for CRUD operations on a database, but don’t enable tight workflow integration or access to draft FHIR resources that may only exist in memory on the EHR client.

3e. Objectives/Deliverables and Target Dates

Ballot the specification as STU in Sept 2020
Publish by Dec. 31, 2020

3i. HL7-Managed Project Document Repository URL:

tbd

3j. Backwards Compatibility

No

3l. Using Current V3 Data Types?

N/A

4a. Products

FHIR Implementation Guide, Guidance (e.g. Companion Guide, Cookbook, etc), New Product Definition

5a. Project Intent

Create new standard, Implementation Guide (IG) will be created/modified

5a. Is the project adopting/endorsing an externally developed IG?

No

5b. Project Ballot Type

STU to Normative

5d. Joint Copyright

Yes

6a. External Project Collaboration

Argonaut Accelerator, SMART

6b. Content Already Developed

75%

6c. Content externally developed?

No

6d. List Developers of Externally Developed Content

SMART, Argonaut

6e. Is this a hosted (externally funded) project?

No

6f. Stakeholders

Standards Development Organizations (SDOs)

6g. Vendors

EHR, PHR, Health Care IT

6h. Providers

Medical Imaging Service, Healthcare Institutions (hospitals, long term care, home care, mental health)

6i. Realm

Universal

7a. Management Group(s) to Review PSS

FHIR

7b. Sponsoring WG Approval Date

Jan 13, 2020

7c. Co-Sponsor Approval Date

Jan 15, 2020

6 Comments

  1. 3c. Security Risk

    No Entry – I don’t think this entry can be blank in a valid PSS.  Did the authors just miss this?  Or is it okay to leave blank?


    1. Edit: According to John Moehrke, this PSS field is intended for something very specific.

      the security field in the PSS is very focused on a very specific risk. That is when the product that HL7 is developing includes software code.

      The IG itself will have a Security Considerations section where concerns around origin checking (implementation considerations, etc) would be mentioned.


      My original comment:

      Thanks for asking, Kathleen.  I'm not sure what to put in the field here, honestly.  With SMART Web Messaging, as well as with standard HTML5 Web Messaging, both sender and receiver should always check the sender message origin when receiving messages. 

      https://en.wikipedia.org/wiki/Web_Messaging#Security-

      Would it be worth paraphrasing this concern in that field, and maybe providing the above link? 

  2. Security WG would request co-sponsorship. Any modification of SMART-on-FHIR, even if that modification is only to the context sharing, is relevant to the security that is provided by SMART-on-FHIR. changing the values in the SMART context through messaging can change the scope of the security context and make it inconsistent with the original scope of the security token used to initiate the SMART-on-FHIR context.

  3. A minor remark: The involved company is T-System, but not T-Systems. This makes a difference.

    1. Thanks, Frank.  I have corrected the list to make it clearer that it's the singular  "The T-System".  (smile)

  4. What is the relationship of this project to FHIRCast? It seems to be covering similar functional space. I don't see mention of this relationship, and don't see involvement with the team working on FHIRCast Isaac Vetter?   Should the Imaging Workgroup be a good co-sponsor given they are the sponsor of FHIRCast?