Global

We've detected that you're in . Would you like to go to the MediCam site?

Frequently Asked Questions

For Users For Institutions

For Users

MediCam enables medical professionals to securely capture clinical images of their patients for such purposes as:

  • Recording the current status and/or progress of a patient’s medical condition,
  • Seeking other medical opinions regarding a particular case,
  • Referring to previous images for comparison and treatment purposes, and
  • Archiving clinical photos for later use in publications, presentations and research.

Here are a couple of possible uses for MediCam:

A burns victim is being treated in the burns unit of a hospital with a badly burnt arm. A nurse dresses the wound a 9am and 4pm each day. At 10am the registrar arrives wants to see how the wound is healing. Now the dressing has to be taken off at great discomfort to the patient, and at great cost to the hospital (in time and materials). If the nurse were to use MediCam to take a photo of the arm while the dressing was being changed at 9am, the pain and cost would be avoided.

A registrar was called from the Emergency Department at 10pm about a 6-year-old boy who had fallen over at home and cut his lip. The Emergency Resident was unable to send a photo of the laceration (despite it being requested by the surgical registrar) because hospital policy would not allow it. The registrar lives in the city and would have had to drive one hour each way to see the child. Instead he decided to put the child on the next morning's operating list without first seeing the laceration. When the registrar examined the child the following day he saw that no surgery was required. Unfortunately the parents were agitated after spending the whole night in the emergency department, and insisted that the child be sutured under general anaesthetic.

Permanent Link
 

The entire MediCam app has been designed with patient privacy at the forefront. Specifically the app ...

  • Asks for patient consent prior to sending/uploading reports.
  • Removes media from the device after it is sent/submitted.
  • Encrypts all patient data before it is emailed.
  • Sends all data, if uploaded, via HTTPS.
  • Provides an audit trail of who has opened a report
  • Time and location stamps all reports.
Permanent Link
 

MediCam uses the default camera on your device. The quality of the image will depend on he quality of the camera and the skill of the photographer. As with taking good photos on your device, please use good lighting and try and keep the camera as steady as you can when taking photos or recording video.

Permanent Link
 

Security is paramount and security measures are inbuilt throughout the MediCam system’s structure. All reports are dated and time stamped, geo-tagged, encrypted and, if uploaded to an third party storage provider, they are securely transmitted over HTTPS. This allows you to transmit and store media in compliance with appropriate security regulatory guidelines. Manipulation, modifying, or changing MediCam media within a report in any manner, is not possible.

Some of the security features include:

  • A "passwordless" user authentication system.
  • All data wiped off your device as soon as it is uploaded or sent.
  • Media cannot be accidentally (or purposefully) uploaded to your device's cloud storage (e.g. iCloud).
  • All "reports" are encrypted using industry standard AES-256 encryption before being emailed.
  • All "reports" uploaded to Box or Dropbox are done so over HTTPS.
  • An audit trail of everyone that accesses a report.
  • An institution can "lock down" key servers with whitelist and blacklists of emails that can and can't access reports.
  • An institution can "lock down" the endpoint so that only users within a network can submit and access reports (if they wish).
Permanent Link
 

Individual images don't have the patients data included in the same file. MediCam PRO users will have the report ID and media ID included in the bottom right corner. The patients details accompany the images in a "report". All reports are automatically tagged with the patient’s name and date of birth, along with relevant secondary identifiers such as location, time, and date tags.

Permanent Link
 

This will be more relevant for those that operate the IT department of an institution (hospital, clinic, etc.). If you want to integrate MediCam reports into a patients medical record, MediCam provides a simple API to allow you to do so.

Ultimately you will need to set up your own "Endpoint". MediCam provides a sample Endpoint application. You will need to write your own middleware to take reports uploaded to the endpoint an move them into your medical record system (MediCam does not perform this integration).

For more details please see How do I set up my own Endpoint?. For even more detail on how endpoints work and how MediCam can be integrated into medical record systems, please see the Integrations Section of this website.

Permanent Link
 

MediCam is fundamentally designed to be a secure, closed network, disallowing sharing outside of this network.

Permanent Link
 

MediCam is optimised to work on both iOS and Android devices, specifically iOS 9+ and Android 4.2+. If you have an earlier operating system, please upgrade your device to the latest operating system.

Permanent Link
 

MediCam is free to receive reports and free to send reports. There is a "MediCam PRO" version with some more advanced features however for most users the free version will be all you need.

MediCam MediCam PRO
Price Free €9 per month
Photos, videos or audio per report 2 10
Photo resolution 1 Megapixel
(1280×960)
3 Megapixel
(2048×1536)
Video resolution Standard Definition
(1280×720)
High Definition
(1920×1080)
Video length 5 seconds 10 seconds
Audio length 20 seconds 120 seconds
Watermark Pink - "Photo taken with the free version (MediCam Basic)" Black - Report and Media ID
Box integration No Yes
Dropbox integration No Yes

Please note: Price may vary depending on what currency you use.

Permanent Link
 

Different hospitals and institutions have different names for some kind of patient identification. Most commonly used is a Unit Record (UR) number. A Medical Record Number (MRN) is also common. In the Patient ID field you can put whatever identifier your institution uses.

In a hospital environment, is is common that wrist or ankle tags contain an identifier. If there is an accompanying barcode, you can use MediCam to scan the barcode in the Patient ID field.

Permanent Link
 

The barcode scanner in MediCam supports the following barcode formats:

  • Aztec
  • Code39
  • Code93
  • Code128 A
  • Code128 B
  • Code128 C
  • Codebar
  • Data Matrix
  • EAN8
  • EAN13
  • ITF
  • ITF-14
  • PDF417
  • QR
  • RSS14 (Android only)
  • UPCA
  • UPCE
Permanent Link
 

Photos are 1 Megapixel (1280×960) for the free version (MediCam Basic) and 3 Megapixel (2048×1536) for MediCam PRO users.

Videos are captured in "Standard Definition" (1080×720) for the free version (MediCam Basic) and "High Definition" (1920×1080) for MediCam PRO users.

Permanent Link
 

Audio files generated are M4A. The can be played back on iOS and Android devices and most media players (e.g. Quicktime).

Permanent Link
 

Audio clips on can be up to 20 seconds long. For MediCam PRO users they can be up to 120 seconds.

Video clips on can be up to 5 seconds long. For MediCam PRO users they can be up to 10 seconds. Video clips are limited to reasonably short clips given they need to be compressed and encrypted on the device. As devices become more powerful we may look to increase the limit. Another factor is the file size. The longer the clips, the bigger the file size. Bigger files take longer to send, longer to download and use more of your data.

Permanent Link
 

There is a trade-off between length and practicality! Ideally MediCam would provide longer videos, however, there are a number of factors that necessitate smaller videos.

  • All videos need to be compressed and encrypted on your device. This takes time. As devices generally get more powerful we might look to increase the limit because we could compress the video more (without loss of quality).
  • The longer the video is, the bigger the report file size. A bigger file size means:
    • It takes longer to send;
    • It uses more data to send;
    • It takes longer for the recipient to receive; and
    • It uses more data to receive (at the recipients cost).
    We obviously want to make MediCam as quick to use as possible.
  • Given more time, users will use it without necessarily adding to the benefit of communicating the intent. Testing has showed that 5 second clips generally are more than enough for the purpose of demonstrating the desired representation.
Permanent Link
 

No.

File size becomes an issue when encrypting and packaging raw files on the device before sending. In future when devices become more powerful we may reevaluate, but for now devices are generally not powerful enough to allow the reports to be sent in a timely manor. Like most things in life, there is a trade off between quality and speed!

The quality of the video and image files is still very high (particularly for MediCam PRO users). There are very few circumstances where the quality will not suffice for all manors of medical use. For the situations where higher resolution is required we remind you that MediCam is not designed to replace traditional clinical photography departments! It's aim is to help doctors deliver better patient care by allowing them to quickly capture, share and store patient photos.

Permanent Link
 

You can attach 2 photos, videos and audio clips per report. If you want to attach more you can upgrade to MediCam PRO and attach up to 10 photos, videos and audio clips.

Please be mindful, the more you attach, the bigger the file size. Bigger files take longer to send, longer to download, use more of your data.

Permanent Link
 

Compressing and encrypting large files needs to be done on the device before a report can be sent. The time it takes to perform the compression is, in large part, a factor of how powerful the device is. As such, only newer iOS and Android devices can do this. In general, the older the device the slower it is to compress.

iOS

Below is a list of iOS devices that support capture of video.

Device Release Date
iPhone 6S September 2015
iPhone 6S Plus September 2015
iPhone SE March 2016
iPhone 7 September 2016
iPhone 7 Plus September 2016
iPad Pro 9.7-Inch November 2015
iPad Pro 12.9-Inch March 2016

Android

As for Android, we base device capability on the version of Android on your device. Note, because some old Android devices can be upgraded there may be some situations where an Android device is not really suitable for video capture. The compression will take a long time to perform.

Version Name Release Date
Android 6 Marshmallow October 2015
Android 7.0 Nougat August 2016
Android 7.1 Nougat August 2016
Permanent Link
 

Compressing and encrypting large files needs to be done on the device before a report can be sent. The time it takes to perform the compression is, in large part, a factor of how powerful the device is. In general, the older the device, the slower it is to compress. If you are finding it is taking too long, it might be time to upgrade your device!

The best iOS device will always be the newest! At this time the iPhone 7 Plus is the top of the line. The Google Pixel is the best Android device we have come across for use with MediCam.

Permanent Link
 

You don't actually "subscribe" to MediCam PRO, you purchase access for a set time period. There is no auto-renew so you don't need to worry about forgetting to cancel your subscription!

Two weeks before a subscription expires, the app will show a message asking you to renew. If you don't renew then, it will send a second reminder three days before it expires and then one more time after it expires. If you want to "unsubscribe" from MediCam PRO simply take no action when you see these reminders. Your access to MediCam PRO will automatically be removed once the current access period ends.

Permanent Link
 

One of the biggest security threats is not someone nefarious hacking into a system, rather it is people using passwords that are easy to guess! People always seem to forget their passwords too! Hence, MediCam uses a "passwordless" log in system.

When you open the app you will be asked to create an account or sign in to an existing account. When you either create an account or sign in, we don't ask for a password. Instead we send you an email with a "magic link" that when opened on a device that has MediCam installed will automatically log you in. It's pretty much the same process you go through when you hit the "forgot password" or "reset password" link on many other websites. We rely on you having secure access to your email.

If you don't have email access on the device you have installed MediCam on, we also provide a 5 digit "Sign in Code" in the email. In the app there is a prompt to enter a "Sign in Code" so you can log in.

For security purposes the "magic link" and the "sign in code" are only valid for 20 minutes and can only be used once. As soon as they are used they will become invalid and you will have to initiate the sign in process again.

If you have requested the email and do not receive it within a few minutes, please check your spam folder.

Permanent Link
 

In order to open a .medicam file you must have the MediCam app (on iOS and Android devices) and you must be signed in to MediCam. If you haven't already done so, download the free MediCam app from the App Store or Google Play, and create an account.

On Android devices, simply tap on the attached file.

On iPhones and iPads, tap on the attached file and select "Copy to MediCam".

Permanent Link
 

If you are using MediCam's Key Server (default), please send a request to [email protected] with the report ID and the email address associated with your MediCam account.

If you are using a custom Key Server, the administrator will be able to look this up. Please contact them.

Permanent Link
 

If you have been sent a report, you can only view photos, videos and audio files through the MediCam app. This is by design, for security purposes. In order to open a .medicam file you must the MediCam app (on iOS and Android devices) and you must be signed in to MediCam.

If you are the one sending the report it is possible to send the files to a Box or Dropbox account (if you have the MediCam PRO). When sending reports to Box or Dropbox the raw files will be transmitted and (presumably) stored securely.

If you set up an institution you will be able to integration with your medical record system to input the raw files. Please see the Integrations Section.

Permanent Link
 

MediCam PRO has Box integration built in. This means that you can use Box to keep an archive of patient media. This is particularly useful for areas of medicine where it is appropriate to document visual changes over time. Box, in conjunction with MediCam, can be used to help you comply with HIPAA and HITECH regulations.

To setup sending to Box, tap on the "Settings" button (on the main form), then tap the "Box" row under the "Integrations" heading. Then tap on the "Log in to Box" button. You will be guided through the process to log in to Box.

To send to Box, on the main form just above the "Submit" button is a "send to" field. Tap on that and select "Box". Upon submitting, the app will upload the report to your Box account.

Note, a "MediCam" directory will be created in your Box account and all reports will be uploaded here. All reports are uploaded over HTTPS. We do not encrypt reports using the key server when submitting to Box as it is assumed that Box stores all reports securely. Please see the Box HIPAA And HITECH Overview And FAQs for more information.

Permanent Link
 

MediCam PRO has Dropbox integration built in. This means that you can use these services to keep and archive of patient media. This is particularly useful for areas of medicine where it is appropriate to pictorial changes over time. Dropbox, in conjunction with, MediCam can use used to help you comply with HIPAA and HITECH.

To setup sending to Dropbox, tap on the "Settings" button (on the main form), then tap the "Dropbox" row under the "Integrations" heading. Then tap on the "Log in to Dropbox" button. You will be guided through logging in to Dropbox.

To send to Dropbox, on the main form just above the "Submit" button is a "send to" field. Tap on that and select "Dropbox". Upon submitting the app will upload the report to your Dropbox account.

Note, a "MediCam" directory will be created in your Dropbox account and all reports will be uploaded here. All reports are uploaded over HTTPS. We do not encrypt reports using the key server when submitting to Box as it is assumed that Box stores all reports securely. Please see Dropbox's Help Center article for more information.

Permanent Link
 

For Institutions

HIPAA stands for the the Health Insurance Portability and Accountability Act of 1996 and HITECH stands for the Health Information Technology for Economic and Clinical Health Act (2009). These two US laws aim to encourage the use of technology in the health care industry while building security and privacy protections for Protected Health Information (PHI).

There is no official HIPAA or HITECH certification and therefore no one tool can say they are "compliant". What we can say is that you can use MediCam in a way that is compliant with HIPAA/HITECH regulations.

If using Box

Box in conjunction with MediCam can use used to help you comply with HIPAA and HITECH. Please see the Box HIPAA And HITECH Overview And FAQs for more information.

If Using Dropbox

Dropbox in conjunction with MediCam can use used to help you comply with HIPAA and HITECH. Please see the HIPAA/HITECH section of the Standards and regulations page on their site. See there "Getting Started with HIPAA" guide and Help Center article for more detailed information.

Permanent Link
 

This will be more relevant for those that operate the IT department of an institution (hospital, clinic, etc.). If you want to integrate MediCam reports into a patients medical record, MediCam provides a simple API to allow you to do so.

Ultimately you will need to set up your own "Endpoint", and it is recommended that you also set up your own "Key Server". MediCam provides a turnkey Docker image for hosting your own Key Server. MediCam also provides a sample Endpoint application. You will need to write your own middleware to take reports uploaded to the endpoint an move them into your medical record system (MediCam does not perform this integration).

For more details please see How do I set up my own Endpoint?. For even more detail on how endpoints work and how MediCam can be integrated into medical record systems, please see the Integrations Section of this website.

Permanent Link
 

This will be more relevant for those that operate the IT department of an institution (hospital, clinic, etc.). If you want to integrate MediCam reports into a patients medical record, MediCam provides a simple API to allow you to do so.

Ultimately you will need to set up your own "Endpoint", and it is recommended that you also set up your own "Key Server". MediCam provides a turnkey Docker image for hosting your own Key Server. MediCam also provides a sample Endpoint application. You will need to write your own middleware to take reports uploaded to the endpoint an move them into your medical record system (MediCam does not perform this integration).

For more details please see How do I set up my own Endpoint?. For even more detail on how endpoints work and how MediCam can be integrated into medical record systems, please see the Integrations Section of this website.

Permanent Link
 

Yes.

We recognise that a number of institutions have this as a restriction imposed on them. We would argue that if the report is encrypted it does not matter where the data travels but that is a side issue here!

You have a few options.

If sending via email

MediCam allows "Reports" to be sent via email direct from the device. Normal email routing will apply. It depends on your ISP and the location of the email server of both sender and recipient as to whether it will "travel" through another country.

If sending to an Institution Endpoint

When sending via an endpoint that you have set up, it will again depend on your ISP. Unless using a VPN it is very unlikely that your ISP would route traffic through another country if both the sender and the endpoint are in the same country.

It is possible to set an endpoint up within an network and thereby making the endpoint an internal IP address. That would mean that only users that are also on the internal network can submit reports and would therefore guarantee that not only would data not leave the country, it would not leave the institutions network.

Permanent Link
 

Short answer: No.

Most electronic medical record systems use an "episode number" for each patient interaction. Generally, this number needs to be generated by the medical record system. Research and testing has shown that to integrate MediCam into such systems slows the process of capturing the "report" much slower, thereby severely reducing the effectiveness of MediCam as a tool. We want to avoid that! It should be possible to use the time stamp of the report and the patients details to generate, or look up, an episode number when a report is added to the medical record.

Permanent Link
 

Short answer: Yes.

Is it necessary?

Before you go to the trouble of doing this, you may want to consider whether it is necessary. There is already, of course, an implicit understanding and ethical obligation that doctors act appropriately. Adding additional technology measures to limit where a report is sent adds undue complexity to the app. We feel it is far easier for a doctor to use the existing built-in address book (in the phone) to email reports to people they know and trust.

However, we understand that, in certain situations, it may be appropriate to limit where MediCam reports can be sent

How the send process works

If you manage the IT department of an institution and it is vital that reports are not shared outside of the organisation, you will need to set up your own "Key Server".

Process when sending via email

When a user composes a "report" in the app and presses the "Submit" button...

  1. The app fetches a "key" from a "Key Server". By default the app uses a Key Server run by MediCam. The Key Server dishes out keys and records who access those keys when a report is opened.
  2. The app packages up the media, the data, and a PDF into a "Report". This Report is then encrypted using the "key". The report is then packaged along with the location of the key server into ".medicam" file. The app opens the default mail program on the device and attaches the encrypted report. The user then picks to whom they want to send the report just like composing a normal email.
  3. When the recipient receives the email they will be prompted to open the .medicam file in the MediCam app.
  4. When they do, the app will open the .medicam file and get the location of the key server. It will then send a request to the key server asking for the key to decrypt the report. Along with this request it sends the users information thereby giving us an "audit trail" of who has accessed the report. Once the key is received the app will decrypt the report and the recipient can see its contents.
Run your own Key Server

If you decide to run your own Key Server it is possible to put a rule in there that means the key server will only give the key to decrypt reports to MediCam users who have an email address that ends in "@myhospital.com" (for example).

To set up your own Key Server, MediCam provides a turnkey Docker image. It allows you to very simply set up and host your own Key Server and can be easily configured to whitelist or blacklist certain email addresses. For example, you could add a rule that says only MediCam users that have an email address that ends in "@myhospital.com" can access the key to unlock reports.

Instruct users to use your key server

The final step is to instruct your users to use the Key Server you have set up. To do this they have to do the following:

  1. Open the MediCam app and tap on "Settings".
  2. Tap on "Institutions Medical Record" and then the "Add" button in the top right.
  3. In "Send type" select "Email", enter the name of your institution (e.g. "My Hospital"), leave the "Endpoint" field blank, and in the "Key Server" field enter the URL of your Key Server (e.g. https://key.medicam.io).
  4. Tap the "Save" button in the top right and go back to the main form.
  5. Now in the main form, in the "Send to" options there will be a "My Hospital" listing under "Institutions". Tap on that.

Now you are able to send reports and it will be encrypted using the Key Server you set up.

For more details on how to setup your own Key Server please see the Integrations Section of this website.

Permanent Link
 

MediCam has been designed to encourage secure capture, dissemination and storage of medical related photos, video and audio clips and it too makes it clear how to do so appropriately. Unfortunately there is not much that can stop inappropriate use (e.g. a doctor can take a screenshot of a picture and share it). However we believe that using MediCam provides more security then the current practice of doctors taking photos in their phones default camera app and sharing insecurely.

We have faith in the medical professional's implicit understanding and ethical obligation that when they receive a MediCam report, they will not inappropriately with that data (e.g. share it on Facebook).

By encouraging MediCam's use within the medical industry we hope to educate medical professionals as to how to share data in a way that protects themselves and others and they can in turn focus on helping people!

Permanent Link
 

MediCam uses RNCryptor for all encryption. RNCryptor is a cross-language AES Encrypter/Decrypter data format.

The data format includes all the metadata required to securely implement AES encryption, as described in "Properly encrypting with AES with CommonCrypto," and iOS 6 Programming Pushing the Limits, Chapter 15. Specifically, it includes:

  • AES-256 encryption
  • CBC mode
  • Password stretching with PBKDF2
  • Password salting
  • Random IV
  • Encrypt-then-hash HMAC

This format was used because it is widely supported. This makes it easier for institutions to integrate MediCam into their medical record systems. There are implementations of RNCryptor in Swift, Objective-C, C, C++, C#, Erlang, Go, Haskell, Java, PHP, Python, Javascript, and Ruby.

Permanent Link
 

A Key Server is used to dish out keys which are used to encrypt reports in the MediCam app prior to sending. See the Methods of Sending/Submitting Reports section above for details on which methods use the Key Server.

For instructions on how to set up your own Key Server please refer to the Running Your Own Key Server section on the Integrations page.

Permanent Link
 

Before explaining how to do this, a brief description of how the MediCam send process works in necessary.

It is possible to send reports to an endpoint via HTTP or HTTPS. It is also possible to specify if the reports should be encrypted in the app prior to being sent. Obviously, it is possible to send reports that are encrypted in the app as well as sending via HTTPS also. This is recommended. If using HTTP you should make sure that reports are always encrypted in the app before being sent. This is a big security vulnerability if not!

Whether a report is send via HTTP or HTTPS is merely a matter of which protocol is specified when an institution is added. "http://endpoint.medicam.io" would send it via HTTP and "https://endpoint.medicam.io" would send it via HTTPS.

Encryption options

Below we will discuss the different processes relating to whether the report is encrypted in the app before sending or not.

Process when sending to an endpoint

Encrypt the report in the app prior to sending

In the diagram above see the pink lines. When a user composes a "report" in the app and presses the "Submit" button...

  1. The app fetches a "key" from a "Key Server". All that Key Server does is dishes out keys and logs who access those keys when a report is opened. When running your own endpoint and encrypting reports before being sent you must setup your own Key Server.
  2. The app packages up the media, the data, and a PDF into a "Report". This Report is then encrypted using the "key". The report is then packaged along with the location of the key server into ".medicam" file. The app sends the report to endpoint (URL).
  3. The endpoint receives the .medicam file and sends a request to the Key Server to get the key to decrypt the report. It then decrypts the report and in turn sends it on.
  4. The endpoint can then be configured to send to report another location (e.g. a patients medical record).
Don't encrypt the report in the app prior to sending.

In the diagram above see the green lines. When a user composes a "report" in the app and presses the "Submit" button...

  1. The app packages up the media, the data, and a PDF into a "Report". The app sends the report to endpoint (URL).
  2. The endpoint receives the Report (zipped file that contains the media, data and PDF).
  3. The endpoint can then be configured to send to report another location (e.g. a patients medical record).
Run your own Endpoint Server

An Endpoint is basically a server that hosts middleware that your IT department will need to create. It simply takes reports uploaded to the endpoint and moves them into your medical record system. MediCam does not perform this integration. MediCam provides a sample Ruby on Rails application that does this. It is an easy task to write something similar in another language.

To trial this system, you do not need to set up your own endpoint yet - we have a test endpoint setup but please note, all reports are visible to the public. DO NOT USE IT FOR LIVE PATIENT DATA.

To test it out do the following:

  1. Open the MediCam app and tap on "Settings".
  2. Tap on "Institutions Medical Record" and then the "Add" button in the top right.
  3. In "Send type" select "Post (Dynamic Key)", enter the name of your institution (e.g. "My Hospital"), in the "Endpoint" field enter "http://endpoint.medicam.io", and leave the "Key Server" field blank.
  4. Tap the "Save" button in the top right and go back to the main form.
  5. Now in the main form, in the "Send to" options there will be a "My Hospital" listing under "Institutions". Tap on that.

Now you are able to send reports to the email you set up. When you "Submit" the report will be uploaded to the demo endpoint. Once finished uploading, if you go to http://endpoint.medicam.io/ you will see the report you uploaded. Obviously under normal circumstances a page like this would not be visible to the public.

Instruct users to use your Endpoint Server (and Key Server if using it)

There is, of course, one more step. We have to instruct users to use the Endpoint you have set up. To do this they have to do the following:

  1. Open the MediCam app and tap on "Settings".
  2. Tap on "Institutions Medical Record" and then the "Add" button in the top right.
  3. In "Send type" select "Post (Dynamic Key)", enter the name of your institution (e.g. "My Hospital"), enter the "Endpoint" URL (e.g. http://endpoint.medicam.io), and in the "Key Server" field enter the URL of your Key Server (e.g. https://key.medicam.io) if you have set up one, otherwise leave it blank.
  4. Tap the "Save" button in the top right and go back to the main form.
  5. Now in the main form, in the "Send to" options there will be a "My Hospital" listing under "Institutions". Tap on that.

Now you are able to send reports and it will be encrypted using the Key Server you set up.


For more details on how to setup your own Key and/or Endpoint Server please see the Integrations Section of this website.

Permanent Link
 

Absolutely. There are different types of trials you may want to try.

App Trial

MediCam is free to use so simply download and give it a go.

If you want to send reports to Box or Dropbox you will need MediCam PRO. You can purchase access for 1 month to trial the feature within the app.

Email Integration Trial

One way of storing reports might be to setting up an email address for your institution (e.g. [email protected]) and getting users to send all reports there. This then becomes a repository of all reports. To open reports you will need to send the report back to a mobile device that has MediCam installed. We recognise that this may not be practical in some situations and therefore we have created Endpoint Integrations (see below).

Once you have set up the email address (e.g. [email protected]), instruct users to do the following:

  1. Open the MediCam app and tap on "Settings".
  2. Tap on "Institutions Medical Record" and then the "Add" button in the top right.
  3. In "Send type" select "Email", enter the name of your institution (e.g. "My Hospital"), in the "Endpoint" field enter the email address you set up (e.g. [email protected]), and leave the "Key Server" field blank.
  4. Tap the "Save" button in the top right and go back to the main form.
  5. Now in the main form, in the "Send to" options there will be a "My Hospital" listing under "Institutions". Tap on that.

Now you are able to send reports to the email you set up. When you "Submit" a report the email dialogue will open and the email address will be pre-populated.

Endpoint Integration Trial

This will be more relevant for those that operate the IT department of an institution (hospital, clinic, etc.). If you want to integrate MediCam reports into a patients medical record, MediCam provides a simple API to allow you to do so.

MediCam provides a sample Endpoint application. You will need to write your own middleware to take reports uploaded to the endpoint an move them into your medical record system (MediCam does not perform this integration). To trial this system, however, you do not need to set this up yet - we have a test endpoint setup but please note, all reports are visible to the public. DO NOT USE IT FOR LIVE PATIENT DATA.

To test it out do the following:

  1. Open the MediCam app and tap on "Settings".
  2. Tap on "Institutions Medical Record" and then the "Add" button in the top right.
  3. In "Send type" select "Post (Dynamic Key)", enter the name of your institution (e.g. "My Hospital"), in the "Endpoint" field enter "http://endpoint.medicam.io", and leave the "Key Server" field blank.
  4. Tap the "Save" button in the top right and go back to the main form.
  5. Now in the main form, in the "Send to" options there will be a "My Hospital" listing under "Institutions". Tap on that.

Now you are able to send reports to the email you set up. When you "Submit" the report will be uploaded to the demo endpoint. Once finished uploading, if you go to http://endpoint.medicam.io/ you will see the report you uploaded. Obviously under normal circumstances a page like this would not be visible to the public.

For more details on how endpoints work and how MediCam can be integrated into medical record systems, please see the Integrations Section of this website.

Permanent Link