Difference between revisions of "Mobile Retrieve Form for Data Capture"
| Line 16: | Line 16: | ||
==Systems Affected== | ==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:''' | '''Actors & Transactions:''' | ||
| − | + | [[Image:mRFD-Actor-Transaction.jpg]] | |
==Specification== | ==Specification== | ||
Revision as of 14:42, 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:
File:MRFD-Actor-Transaction.jpg
Specification
Profile Status: Final Text <Replace "Final Text" with "Trial Implementation" or "Public Comment" as appropriate.>
Documents:
<Provide direct links to the specific volumes or supplements, and list the volume sections relevant to this profile. This is a simple inventory of official normative and informative text. If you would like to provide a reading guide or walkthrough of what is in each of the different sections for implementers or users, do that in the Profile FAQ or the Profile Implementation Page linked below. If the profile uses transactions from multiple Tech. Frameworks, repeat the structure below.>
IHE Radiology Technical Framework:
Underlying Standards:
<list all the standards on which the profile is based; if possible with links to sources>
See Also
<The following sections can be left out if there is nothing to point to. This is just to show where such information can go.>
Related Profiles
<List profiles this one depends on, profiles that depend on this one, profiles that are synergistic with this one. Start with the name of the other profile as a link and then explain the relationship.>
- Reporting Workflow [RWF] may use Evidence Documents as inputs to the reporting process.
- Simple Image & Numeric Reports [SINR] may include data copied from Evidence Documents.
- Cross-enterprise Document Sharing for Imaging [XDS-I] can be used to share Evidence Documents between sites over a network.
- Portable Data for Imaging [PDI] can store Evidence Documents on media such as CDs.
- Import Reconciliation Workflow [IRWF] can fix patient ids, etc. of Evidence Documents when importing.
Consumer Information
The Profile FAQ Template answers typical questions about what the Profile does. <Replace the link with a link to the actual FAQ page for the Profile>
The Profile Purchasing Template describes considerations when purchasing equipment to deploy this Profile. <Replace the link with a link to the actual Purchasing page for the Profile>
Implementer Information
The Profile Implementation Template provides additional information about implementing this Profile in software. <Replace the link with a link to the actual Implementation page for the Profile>
Reference Articles
<List References (good and bad) (with link if possible) to Journal Articles that mention IHE's work (and hopefully include some analysis). Go ahead, Google: IHE <Profile Name> abstract or Google: IHE <Profile Name> and under the "more" select "Scholar". You might be surprised. >