Difference between revisions of "201801 IHE-on-FHIR"
Stephenmoore (talk | contribs) (→Roles) |
Stephenmoore (talk | contribs) (→Roles) |
||
| Line 34: | Line 34: | ||
This track will be further refined based on the [http://wiki.ihe.net/index.php/Category:FHIR IHE Profiles that leverage FHIR], not including those more dedicated tracks, and the participation. The wiki reference above gives a full list of IHE profiles that leverage FHIR. This is a short list that excludes the tracks already proposed for January, 2018: | This track will be further refined based on the [http://wiki.ihe.net/index.php/Category:FHIR IHE Profiles that leverage FHIR], not including those more dedicated tracks, and the participation. The wiki reference above gives a full list of IHE profiles that leverage FHIR. This is a short list that excludes the tracks already proposed for January, 2018: | ||
| − | * | + | * Mobile Alert Communication Management (mACM) |
| + | ** The Mobile Alert Communication Management (mACM) Profile provides the infrastructural components needed to send short, unstructured text alerts to human recipients and can record the outcomes of any human interactions upon receipt of the alert. The mACM Profile also allows for a feedback mechanism to determine the status of an alert through the use of alert statuses. | ||
| + | * Mobile Access to Health Documents (MHD) | ||
| + | ** The Mobile access to Health Documents (MHD) Profile defines one standardized interface to health documents (a.k.a. an Application Programming Interface (API)) for use by mobile devices so that deployment of mobile applications is more consistent and reusable. MHD it enables simplified access by mobile devices to an XDS (or a similar) document management environment containing health information. | ||
| + | * Mobile Cross-Enterprise Document Data Element Extraction (mXDE) | ||
| + | ** The Mobile Cross-Enterprise Document Data Element Extraction (mXDE) Profile provides the means to access data elements extracted from shared structured documents. This is intended to support data provenance. | ||
| + | |||
IHE will provide experienced IHE-Connectathon staff with tooling used at [http://www.iheusa.org/ihe-connectathon-registration IHE Connectation]. | IHE will provide experienced IHE-Connectathon staff with tooling used at [http://www.iheusa.org/ihe-connectathon-registration IHE Connectation]. | ||
Revision as of 16:01, 1 November 2017
IHE-on-FHIR
Submitting WG/Project/Implementer Group
Driven by IHE International in coordination with IHE-Connectathon
Justification
To support engagement at FHIR Connectathon on the IHE Profiles that leverage FHIR.
Shall not duplicate more focused and dedicate tracks. These other tracks are encouraged and every effort will be made to coordinate IHE engagement with them:
- 201801 Care Plan
- 201801 Medical Device and Implantables Tracking using UDI
- 201801 Provider Directory
- 201801 Patient Track
Also not intended to be testing non-FHIR based IHE profiles. Testing will leverage IHE-Connectathon tools, but will not be considered as comprehensive as IHE-Connectathon
Zulip thread for refinement
https://chat.fhir.org/#narrow/stream/ihe/topic/January.20Connectathon.20-.20IHE-on-FHIR
Proposed Track Lead
See Connectathon_Track_Lead_Responsibilities
- Steve Moore (MooreS@mir.wustl.edu)
- John Moehrke (JohnMoehrke@gmail.com) -- skype id = johnmoehrke
Expected participants
Roles
This track will be further refined based on the IHE Profiles that leverage FHIR, not including those more dedicated tracks, and the participation. The wiki reference above gives a full list of IHE profiles that leverage FHIR. This is a short list that excludes the tracks already proposed for January, 2018:
- Mobile Alert Communication Management (mACM)
- The Mobile Alert Communication Management (mACM) Profile provides the infrastructural components needed to send short, unstructured text alerts to human recipients and can record the outcomes of any human interactions upon receipt of the alert. The mACM Profile also allows for a feedback mechanism to determine the status of an alert through the use of alert statuses.
- Mobile Access to Health Documents (MHD)
- The Mobile access to Health Documents (MHD) Profile defines one standardized interface to health documents (a.k.a. an Application Programming Interface (API)) for use by mobile devices so that deployment of mobile applications is more consistent and reusable. MHD it enables simplified access by mobile devices to an XDS (or a similar) document management environment containing health information.
- Mobile Cross-Enterprise Document Data Element Extraction (mXDE)
- The Mobile Cross-Enterprise Document Data Element Extraction (mXDE) Profile provides the means to access data elements extracted from shared structured documents. This is intended to support data provenance.
IHE will provide experienced IHE-Connectathon staff with tooling used at IHE Connectation.
Role 1 Name
Scenarios
Scenario Step 1 Name
- Action:
- Precondition:
- Success Criteria:
- Bonus point:
TestScript(s)
Security and Privacy Considerations
unknown at this time
