MIT-LCP / MIT-LCP/mimic-code

Regarding the Use of LLMs like GPT (I have read the DUA)

Open
#1,890 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Jupyter Notebook
Stars
3.4k
Forks
1.7k
PR merge metrics
No merged PRs in 30d

Description

Hi,

I have read this post: https://physionet.org/news/post/gpt-responsible-use, so I know I shouldn't pass any data through the OpenAI API.

However, I was wondering if I could use a closed version of GPT model. We have our own GPT service that is governed by the University and not sharing any data back to OpenAI (it's a one way traffic). I will not go into more details as this is a public thread, but I have sent the links to the explanations of our models to your email addresses contact@physionet.org and Dr Johnson's address (sorry for being annoying as this is one of the urgent matters).

Overall I believe that our university GPT service should conform your policy, as it is very much similar to the Azure OpenAI service and other options you recommened in the physionet post. However, I do want to have a confirmation from you for a green light before I do anything on this task.

Thank you so much for reading and replying, I apologise if this has been annoying.

Sincerely.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked PhysioNet responsible-use post and the model explanations sent to the listed email addresses. There is no file, test, or implementation entry point mentioned; the issue is done only when maintainers confirm whether the university-managed GPT service is permitted under the policy.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
10/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.