Patient is not already registered for ASL Each scenario should provide sufficient description that participants can appropriately construct their software in advance to prepare to interoperate during the connectathon.įrom a clinical system or patient app, submit required clinical details to register a patient for an ASL via FHIR API. Please include information here regarding how much advance preparation will be required if creating a client and/or server.ĭescribe the different scenarios participating systems can engage in during the connctathon. Kate Ebrill will be speaking to vendors at the Dec Connectathon to confirm attendance (primary, acute care vendors).Ī recording of the orientation webinar will be uploaded soon.ĭescribe each type of system that could participate in the track Potential tracks that could be related include subscriptionsĮRx Script Exchange (prescription exchange service – Fred IT) ![]() The current implementation leverages the exiting FHIR standard for Medication Request with Australian extensions/localisation ![]() This track will use what version of FHIR. This track aims to offer all vendors an opportunity to work together, but also an opportunity for vendors not currently familiar with FHIR or active in the FHIR community to work with other vendors who are experienced with FHIR. ![]() ePrescribing changes to support paperless prescriptions impacts all vendors across acute, primary and residential aged care. Integration to the new ePrescribing APIs is a key success factor in rolling out paperless prescriptions. Use of FHIR as the vendor API has enabled maintaining a central repository for prescriptions in Australia, whilst supporting the patient's choice of attending any pharmacy in the country to obtain supply.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |