com.github.vitalsoftware.scalaredox.models
Meta
Related Docs:
object Meta
| package models
Data model. E.g. Scheduling, Results
Type of event. E.g. New, Update
DateTime of the event. ISO 8601 Format
Flag as a test message
Where the message originated. Included in messages from Redox
List of destinations to send your message to. All messages must have at least one destination. Queries accept only one destination. Required when sending data to Redox
Record in Redox that corresponds to the communication sent from the source to Redox. Included in messages from Redox
Record in Redox that corresponds to the communication sent from Redox to your destination. Included in messages from Redox
Code for the facility related to the message. Only use this field if a health system indicates you should. The code is specific to the health system's EHR and might not be unique across health systems. In general, the facility fields within the data models (e.g. OrderingFacility) are more reliable and informative.
Indicates that a limit was reached, and not all data was returned. If true, the sender may want to restrict the parameters of the request in order to match fewer results.
Data model.
Data model. E.g. Scheduling, Results
List of destinations to send your message to.
List of destinations to send your message to. All messages must have at least one destination. Queries accept only one destination. Required when sending data to Redox
DateTime of the event.
DateTime of the event. ISO 8601 Format
Type of event.
Type of event. E.g. New, Update
Code for the facility related to the message.
Code for the facility related to the message. Only use this field if a health system indicates you should. The code is specific to the health system's EHR and might not be unique across health systems. In general, the facility fields within the data models (e.g. OrderingFacility) are more reliable and informative.
Indicates that a limit was reached, and not all data was returned.
Indicates that a limit was reached, and not all data was returned. If true, the sender may want to restrict the parameters of the request in order to match fewer results.
Record in Redox that corresponds to the communication sent from the source to Redox.
Record in Redox that corresponds to the communication sent from the source to Redox. Included in messages from Redox
Where the message originated.
Where the message originated. Included in messages from Redox
Flag as a test message
Record in Redox that corresponds to the communication sent from Redox to your destination.
Record in Redox that corresponds to the communication sent from Redox to your destination. Included in messages from Redox
Request/response header meta-data
Data model. E.g. Scheduling, Results
Type of event. E.g. New, Update
DateTime of the event. ISO 8601 Format
Flag as a test message
Where the message originated. Included in messages from Redox
List of destinations to send your message to. All messages must have at least one destination. Queries accept only one destination. Required when sending data to Redox
Record in Redox that corresponds to the communication sent from the source to Redox. Included in messages from Redox
Record in Redox that corresponds to the communication sent from Redox to your destination. Included in messages from Redox
Code for the facility related to the message. Only use this field if a health system indicates you should. The code is specific to the health system's EHR and might not be unique across health systems. In general, the facility fields within the data models (e.g. OrderingFacility) are more reliable and informative.
Indicates that a limit was reached, and not all data was returned. If true, the sender may want to restrict the parameters of the request in order to match fewer results.