Difference between revisions of "Mobile Retrieve Form for Data Capture"
| Line 27: | Line 27: | ||
'''Profile Status:''' [[Comments| Trial Implementation]] | '''Profile Status:''' [[Comments| Trial Implementation]] | ||
| − | '''Documents:''' [http://www.ihe.net/Technical_Frameworks/#QRPH# Mobile Retrieve Form for Data Capture Profile] | + | '''Documents:''' [http://www.ihe.net/Technical_Frameworks/#QRPH # Mobile Retrieve Form for Data Capture Profile] |
'''Underlying Standards:''' | '''Underlying Standards:''' | ||
Revision as of 14:51, 21 July 2017
Summary
The Mobile Retrieve Form for Data Capture (mRFD) Profile provides a method for gathering data within a user’s current application to meet the requirements of an external system. mRFD supports RESTful retrieval of forms from a form source, display and completion of a form, and return of instance data from the display application to the source application. The workflows defined in this profile are based on those defined by the Retrieve Form for Data Capture (RFD) profile.
Benefits
- Ability to fill in form data within a user's current application
- Standardized interaction for filling form data
Details
The Mobile Retrieve Form for Data Capture (mRFD) profile provides a method for gathering data within a user’s current application to meet the requirements of an external system. mRFD supports the retrieval of forms from a form source, the display and completion of a form and return of instance data from the display application to the source application.
The profile was created in conjunction with HL7 and uses the SMART on FHIR EHR Launch capacity as a generic framework for access to external web applications.
mRFD also allows dynamic data collection, both from within the form-requesting EHR, and from external sources that may have useful data that can be retrieved via secured RESTful transactions.
Systems Affected
- EHR systems may find mRFD to be an effective method of launching external applications.
- Web application developers may find the standardized security and authentication steps within mRFD to provide a clear direction for integration with a variety of data sources.
Actors & Transactions:
Specification
Profile Status: Trial Implementation
Documents: # Mobile Retrieve Form for Data Capture Profile
Underlying Standards:
- HL7 FHIR STU3
- Hypertext Transfer Protocol - HTTP/1.1
- Hypertext Transfer Protocol - HTTP/2
- Uniform Resource Identifier (URI): Generic Syntax
- The application/json Media Type for JavaScript Object Notation (JSON)
- Additional HTTP Status Codes
- Argonauts SMART on FHIR
- HL7 Collaboration for SMART
See Also
Related Profiles
- Retrieve Form for Data Capture [RFD] may be in use for exchange of a CDA for form population.
- Structured Data Capture [SDC] may be in use for exchange of a structured form.