Difference between revisions of "201605 SMART-ca on FHIR"
(Created page with "{{subst::Template for FHIR Connectathon Track Proposals}}") |
|||
| (4 intermediate revisions by the same user not shown) | |||
| Line 5: | Line 5: | ||
==Submitting WG/Project/Implementer Group== | ==Submitting WG/Project/Implementer Group== | ||
| − | + | FHIR Infrastructure/Gevity Consulting | |
==Justification== | ==Justification== | ||
<!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. --> | <!--Why is this an important track to include in the connectathon - include implementer need, impact on ballot, FMM readiness of the resources, etc. --> | ||
| + | The SMART on FHIR specification has been well-exercised and is building significant traction in the US. However, the need for SMART is global and, at present, SMART is tied to the DAF profiles which are U.S.-centric, including the use of U.S.-specific terminologies and extensions. In principle, SMART can be easily extended to accommodate different underlying profiles. This Connectathon (based in Canada) will attempt to exercise both existing and new SMART apps atop both Canadian and the standard US profiles. The intent of the Canadian profiles will be to align closely with DAF, diverging only when essential for Canadian needs. | ||
==Proposed Track Lead== | ==Proposed Track Lead== | ||
<!-- Name, email and Skype id of individual who will coordinate the track at the connectathon --> | <!-- Name, email and Skype id of individual who will coordinate the track at the connectathon --> | ||
See [[Connectathon_Track_Lead_Responsibilities]] | See [[Connectathon_Track_Lead_Responsibilities]] | ||
| + | Lloyd McKenzie (lmckenzie@gevityinc.com) Skype:lmckenzi | ||
==Expected participants== | ==Expected participants== | ||
<!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track --> | <!-- List of the individuals and/or organizations that have indicated a desire to attend the connectathon and implement this track --> | ||
| + | TBD | ||
==Roles== | ==Roles== | ||
<!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on --> | <!-- Roles are sets of functionality (generally defined by a Conformance resource) that a single system can take on --> | ||
| − | === | + | |
| + | ===Smart Client=== | ||
<!-- Provide a description of the capabilities this role will have within the connectathon --> | <!-- Provide a description of the capabilities this role will have within the connectathon --> | ||
| + | Any FHIR Client that has been modified to support working on Canadian-adapted DAF profiles for Immunization, MedicationOrder, MedicationStatement, Patient and Observation resources | ||
| + | |||
| + | ===FHIR Server=== | ||
| + | This will be a generic FHIR server capable of storing Immunization, MedicationOrder, MedicationStatement, Patient and Observation resources | ||
==Scenarios== | ==Scenarios== | ||
<!-- What will be the actions performed by participants? --> | <!-- What will be the actions performed by participants? --> | ||
| + | Connect to a server and perform SMART App functions while configured to use the standard US profile. Then do the same while configured to use the Canadian profile. Filter using appropriate drug, observation code and other terminologies. | ||
| − | + | Note: All scenarios involve the use of Canadianized versions of the existing SMART profile. The current proposed version of this profile can be found here: [[File:Smart_1.3_-_CA.docx]] | |
| − | : | ||
| − | |||
| − | : | ||
| − | |||
| − | + | ===Scenario Step 1 - Canadian SMART=== | |
| + | :Action: | ||
| + | # Smart App connects to client and confirms it supports the Canadian SMART profile | ||
| + | # Smart App accesses medication, immunization and/or patient data using the SMART FHIR interface, querying using Canadian code systems and renders it within the application | ||
| + | :Precondition | ||
| + | * SMART-enabled client system possesses data that comply with the Canadian SMART profiles (i.e. using Canadian terminologies for drugs, vaccines, etc.) | ||
| + | * SMART app is able to adapt to the SMART profile declared by the SMART-enabled client system | ||
| + | :Success Criteria | ||
| + | * Data successfully retrieved and displayed | ||
==TestScript(s)== | ==TestScript(s)== | ||
Latest revision as of 03:49, 14 April 2016
Track Name
Submitting WG/Project/Implementer Group
FHIR Infrastructure/Gevity Consulting
Justification
The SMART on FHIR specification has been well-exercised and is building significant traction in the US. However, the need for SMART is global and, at present, SMART is tied to the DAF profiles which are U.S.-centric, including the use of U.S.-specific terminologies and extensions. In principle, SMART can be easily extended to accommodate different underlying profiles. This Connectathon (based in Canada) will attempt to exercise both existing and new SMART apps atop both Canadian and the standard US profiles. The intent of the Canadian profiles will be to align closely with DAF, diverging only when essential for Canadian needs.
Proposed Track Lead
See Connectathon_Track_Lead_Responsibilities Lloyd McKenzie (lmckenzie@gevityinc.com) Skype:lmckenzi
Expected participants
TBD
Roles
Smart Client
Any FHIR Client that has been modified to support working on Canadian-adapted DAF profiles for Immunization, MedicationOrder, MedicationStatement, Patient and Observation resources
FHIR Server
This will be a generic FHIR server capable of storing Immunization, MedicationOrder, MedicationStatement, Patient and Observation resources
Scenarios
Connect to a server and perform SMART App functions while configured to use the standard US profile. Then do the same while configured to use the Canadian profile. Filter using appropriate drug, observation code and other terminologies.
Note: All scenarios involve the use of Canadianized versions of the existing SMART profile. The current proposed version of this profile can be found here: File:Smart 1.3 - CA.docx
Scenario Step 1 - Canadian SMART
- Action:
- Smart App connects to client and confirms it supports the Canadian SMART profile
- Smart App accesses medication, immunization and/or patient data using the SMART FHIR interface, querying using Canadian code systems and renders it within the application
- Precondition
- SMART-enabled client system possesses data that comply with the Canadian SMART profiles (i.e. using Canadian terminologies for drugs, vaccines, etc.)
- SMART app is able to adapt to the SMART profile declared by the SMART-enabled client system
- Success Criteria
- Data successfully retrieved and displayed
