Fast healthcare interoperability resources model for user interface generation
An application file defines a first data object that identifies a fast healthcare interoperability resources (FHIR) server and a second data object that identifies a data type associated with the FHIR server. Based on the first data object and the second data object, a FHIR model requests data of the data type from the FHIR server. The FHIR server provides the requested data, which is received by the FHIR model. Based on the received data, the FHIR model generates data in a user interface (UI) control format and provides the generated data to a UI module that causes a UI to be presented. The FHIR model supports binding of complete entities such as patients or organizations to a UI. This binding enables the requesting of whole entities from a FHIR endpoint, provision of the entity data to the UI, and updating the FHIR data.
1. A method comprising:
accessing, at a client device, a first data object that identifies a fast healthcare interoperability resources (FHIR) server;
accessing, at the client device, a second data object that identifies a data type associated with the FHIR server;
based on the first data object and the second data object, requesting, via a network, a third data object of the data type from the FHIR server;
in response to the request, receiving, at the client device and via the network, the third data object from the FHIR server, the third data object being in a FHIR format;
generating, at the client device and based on the third data object, a fourth data object in a user interface control format; and
causing, by one or more hardware processors of the client device, a user interface to be presented based on the fourth data object.
2. The method of claim 1 , wherein:
the second data object is in extensible markup language (XML) format; and
the second data object identifies a component of the user interface that is bound to the data type.
3. The method of claim 1 , wherein the third data object contains a plurality of properties for an entity.
4. The method of claim 1 , wherein the third data object contains a plurality of properties for each of a list of entities.
5. The method of claim 1 , wherein the third data object is in a flat data format and the fourth data object is in a tree data format.
6. The method of claim 1 , wherein:
the second data object identifies a field of the data type;
the third data object comprises a value for the field; and
the user interface comprises a selector having an initially-selected value for the field set to the value, the selector operable to change the value of the field.
7. The method of claim 6 , further comprising:
receiving, via the selector, an updated value for the field of the third data object;
providing, to the FHIR server via the network, the updated value for the field of the third data object; and
receiving, from the FHIR server via the network, a confirmation that the third data object is updated to use the updated value.
8. The method of claim 1 , wherein:
the second data object identifies a number of records to retrieve; and
the requesting of the third data object comprises requesting the number of records.
9. The method of claim 1 , further comprising:
accessing, at the client device, a fifth data object that identifies a second data type associated with the FHIR server;
based on the first data object and the fifth data object, requesting, via the network, a sixth data object of the second data type from the FHIR server;
in response to the request for the sixth data object, receiving, at the client device and via the network, the sixth data object from the FHIR server, the sixth data object being in a second FHIR format; and
generating, at the client device and based on the sixth data object, a seventh data object in the user interface control format; and
wherein the causing of the user interface to be presented further causes the user interface to be presented based on the seventh data object.
10. The method of claim 9 , wherein the sixth data object comprises a count of records on the FHIR server.
11. A system comprising:
a memory that stores instructions; and
one or more processors configured by the instructions to perform operations comprising:
accessing a first data object that identifies a fast healthcare interoperability resources (FHIR) server;
accessing a second data object that identifies a data type associated with the FHIR server;
based on the first data object and the second data object, requesting, via a network, a third data object of the data type from the FHIR server;
in response to the request, receiving, via the network, the third data object from the FHIR server, the third data object being in a FHIR format;
generating, based on the third data object, a fourth data object in a user interface control format; and
causing a user interface to be presented based on the fourth data object.
12. The system of claim 11 , wherein:
the second data object is in extensible markup language (XML) format; and
the second data object identifies a component of the user interface that is bound to the data type.
13. The system of claim 11 , wherein the third data object contains a plurality of properties for an entity.
14. The system of claim 11 , wherein the third data object contains a plurality of properties for each of a list of entities.
15. The system of claim 14 , wherein the third data object is in a flat data format and the fourth data object is in a tree data format.
16. A non-transitory computer-readable medium that stores instructions that, when executed by one or more processors, cause the one or more processors to perform operations comprising:
accessing a first data object that identifies a fast healthcare interoperability resources (FHIR) server;
accessing a second data object that identifies a data type associated with the FHIR server;
based on the first data object and the second data object, requesting, via a network, a third data object of the data type from the FHIR server;
in response to the request, receiving, via the network, the third data object from the FHIR server, the third data object being in a FHIR format;
generating, based on the third data object, a fourth data object in a user interface control format; and
causing a user interface to be presented based on the fourth data object.
17. The computer-readable medium of claim 16 , wherein:
the second data object is in extensible markup language (XML) format; and
the second data object identifies a component of the user interface that is bound to the data type.
18. The computer-readable medium of claim 16 , wherein the third data object contains a plurality of properties for an entity.
19. The computer-readable medium of claim 16 , wherein the third data object contains a plurality of properties for each of a list of entities.
20. The computer-readable medium of claim 16 , wherein the third data object is in a flat data format and the fourth data object is in a tree data format.